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

Previous Next

Full log

View this message in rfc822 format

From: Pip Cet <pipcet <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 36649 <at> debbugs.gnu.org, larsi <at> gnus.org, eggert <at> cs.ucla.edu
Subject: bug#36649: 27.0.50; pure space and pdumper
Date: Sat, 22 Aug 2020 08:55:21 +0000

[Message part 1 (text/plain, inline)]

On Fri, Aug 21, 2020 at 1:47 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Pip Cet <pipcet <at> gmail.com>
> > Date: Fri, 21 Aug 2020 13:04:47 +0000
> > Cc: 36649 <at> debbugs.gnu.org, Paul Eggert <eggert <at> cs.ucla.edu>
> >
> > On Fri, Aug 21, 2020 at 12:52 PM Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
> > > I didn't read this thread closely, but it seems like the conclusion that
> > > this patch should have been applied.  (It removes pure space,
> > > apparently?)
> > >
> > > The patch never was applied, though -- should it be applied now?
> >
> > I believe it's best to be careful with this one. Pure space affects GC
> > in subtle ways, and it also affects performance.
> >
> > See this thread:
> > https://lists.gnu.org/archive/html/emacs-devel/2019-07/msg00588.html
> >
> > I'd be happy to set up a separate branch for removing pure space if
> > that's preferred.
>
> What do we do with unexec builds, which are still supported?

I think that's an important question, but I don't think it's strongly
connected to pure space.

In fact, it appears like unexec builds are currently broken on master,
and on this GNU/Linux machine, I've got to force use of HYBRID_MALLOC
to get an unexec build starting at all. But, having done that, it
works with and without the patch, at first glance.

Rebased patch attached (but I just noticed  the commit message is no
longer complete).

[0001-Remove-pure-space.patch (text/x-patch, attachment)]

Previous Next

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