[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Merging scratch/no-purespace to remove unexec and purespace
From: |
Gerd Möllmann |
Subject: |
Re: Merging scratch/no-purespace to remove unexec and purespace |
Date: |
Wed, 18 Dec 2024 15:03:19 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Andrea Corallo <acorallo@gnu.org> writes:
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>>>> Cc: emacs-devel@gnu.org, Pip Cet <pipcet@protonmail.com>, Stefan Monnier
>>>> <monnier@iro.umontreal.ca>
>>>> Date: Tue, 17 Dec 2024 18:56:05 +0100
>>>>
>>>> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>>>>
>>>> > Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>>>> >
>>>> >> I think check_comp_unit_relocs should be removed in the branch. What's
>>>> >> left of it the branch, checks in master if everything has been
>>>> >> put in purespace which should be there. IIUC correctly, of course.
>>>> >
>>>> > Patch attached.
>>>>
>>>> Pushed. Complaints to me please.
>>>
>>> I'd like at least Andrea to take a look and confirm.
>>
>> It's 81fc23b5d6a60ca4f3d269ab2c88eb9a850bac4c
>
> Hi Gerd,
>
> looking at the commit now, why do you think 'check_comp_unit_relocs'
> should be removed?
>
> Even if now the situation is simpler 'check_comp_unit_relocs' is still
> performing some sanity checks like if lambdas are all been fixed-up and
> present in 'comp_u->lambda_gc_guard_h'.
>
> Andrea
Hi Andrea.
The check you mention checks something that I don't see how it could
happen. (With the usual disclaimers, because it's been some time since I
was in that code for igc.)
When we comp--register-lambda the code putting the result of make_subr
into the hash table and putting it in data_relocs (in the branch) is
just a handful of lines apart. I thereforeo thought we could do without.
- Merging scratch/no-purespace to remove unexec and purespace, Stefan Kangas, 2024/12/17
- Re: Merging scratch/no-purespace to remove unexec and purespace, Gerd Möllmann, 2024/12/17
- Re: Merging scratch/no-purespace to remove unexec and purespace, Gerd Möllmann, 2024/12/17
- Re: Merging scratch/no-purespace to remove unexec and purespace, Gerd Möllmann, 2024/12/17
- Re: Merging scratch/no-purespace to remove unexec and purespace, Gerd Möllmann, 2024/12/17
- Re: Merging scratch/no-purespace to remove unexec and purespace, Eli Zaretskii, 2024/12/17
- Re: Merging scratch/no-purespace to remove unexec and purespace, Gerd Möllmann, 2024/12/17
- Re: Merging scratch/no-purespace to remove unexec and purespace, Andrea Corallo, 2024/12/18
- Re: Merging scratch/no-purespace to remove unexec and purespace,
Gerd Möllmann <=
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2024/12/18
- Re: Merging scratch/no-purespace to remove unexec and purespace, Gerd Möllmann, 2024/12/18
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2024/12/18
- Re: Merging scratch/no-purespace to remove unexec and purespace, Andrea Corallo, 2024/12/18
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2024/12/19
- Re: Merging scratch/no-purespace to remove unexec and purespace, Andrea Corallo, 2024/12/19
- Re: Merging scratch/no-purespace to remove unexec and purespace, Stefan Kangas, 2024/12/19
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2024/12/19
- Re: Merging scratch/no-purespace to remove unexec and purespace, Stefan Kangas, 2024/12/19
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2024/12/19