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

Previous Next

Package: emacs;

Reported by: Pip Cet <pipcet <at> gmail.com>

Date: Sun, 14 Jul 2019 14:27:01 UTC

Severity: wishlist

Tags: patch

Found in version 27.0.50

Done: Pip Cet <pipcet <at> protonmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: eggert <at> cs.ucla.edu, rpluim <at> gmail.com, stefan <at> marxist.se,
 schwab <at> linux-m68k.org, pipcet <at> gmail.com, 36649 <at> debbugs.gnu.org, larsi <at> gnus.org,
 akrl <at> sdf.org
Subject: Re: bug#36649: 27.0.50; pure space and pdumper
Date: Wed, 12 May 2021 15:07:42 -0400
>> > Keeping unexec doesn't mean breaking it.  If we believe someone might
>> > need that configuration, then we should give them a full-fledged
>> > Emacs, not a crippled one.
>> 
>> Removing pure space from unexec builds doesn't make them
>> crippled, AFAIK.
>
> I just don't want to risk that, not at all.  Because if we are missing
> something, it will require efforts I'd rather put elsewhere.

I can see a risk that removing purespace will break unexec because of
some oversight of some detail somewhere (simply because it's
a configuration that's basically never tested), but I can't imagine the
breakage to be hard to fix: running without purespace has been used
during the bootstrap for many many years, both with pdump and with
unexec, so it's really not "special".

The only real consequence will be a slightly worse performance, but no
worse than what we get with pdump anyway ;-)


        Stefan





This bug report was last modified 199 days ago.

Previous Next


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