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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pip Cet <pipcet <at> gmail.com>
Cc: 36649 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
Subject: bug#36649: 27.0.50; pure space and pdumper
Date: Sat, 02 Jul 2022 12:06:42 +0300

> From: Pip Cet <pipcet <at> gmail.com>
> Date: Sat, 2 Jul 2022 08:55:46 +0000
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 36649 <at> debbugs.gnu.org
> 
> On Fri, Jul 1, 2022 at 6:58 PM Stefan Monnier <monnier <at> iro.umontreal.ca> wrote:
> > >> That means keeping purespace and hence not applying the patch.
> > >> Why would we want to keep purespace in the unexec build?
> > > This was discussed at length, I think in this bug as well.
> > I've seen it stated in this thread, but never explained, no.
> 
> FWIW, I don't recall any reason why it shouldn't work with unexec,
> either. To the best of my recollection, unexec was generally broken at
> the time I wrote the patch; I fixed unexec and then it worked without
> purespace, but the unexec fixes never made it into master until Eli
> re-did them a while later.

Basically, I don't want us to drop the pure space in the unexec
builds, whether it makes sense to the rest of you or not.  So there
are two alternatives: either drop pure space only for the pdumper
build, or wait for us to remove the unexec support and drop pure space
then.

Previous Next

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