GNU bug report logs - #36649
27.0.50; pure space and pdumper

Previous Next

Full log

Message #355 received at 36649 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: luangruo <at> yahoo.com, 36649 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca,
 pipcet <at> gmail.com
Subject: Re: bug#36649: 27.0.50; pure space and pdumper
Date: Sat, 02 Jul 2022 20:31:44 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: luangruo <at> yahoo.com,  pipcet <at> gmail.com,  36649 <at> debbugs.gnu.org,
>   monnier <at> iro.umontreal.ca
> Date: Sat, 02 Jul 2022 19:23:24 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > No, I'm okay with having the purespace removed from the pdumper
> > builds, if the unexec build can still use it.  AFAIU, that's the
> > "behind several ifdefs" alternative.
> 
> One reason to get rid of pure space is to get rid of all the calls to
> build_pure_c_string etc etc that litter the code, but just disabling
> pure space in pdump doesn't help us with that.  (And the reason we want
> to do that is to make the code easier to approach for people.)

Yes, I understand that this change has 2 parts: the syntactic part
(removing the calls to *pure* functions from our sources) and the part
that removes the use of purespace.  The first part will have to wait
until we remove the unexec support; the second part can either wait
till then, or we can stop using purespace in the pdumper builds now.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.