Re: Objects that can't be purified during dumping

[Lynn Winebarger <owinebar@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]

On Sat, Jul 23, 2022, 9:27 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Lynn Winebarger <owinebar@gmail.com>
> > Date: Sat, 23 Jul 2022 08:19:35 -0400
> >
> > In my quest to have a "fully loaded" emacs, I'm attempting to dump a
> version that loads about 2400 features
> > in site-load.el.
>
> Dump how? with the portable dumping?  If so, we don't yet fully
> support re-dumping, although it's a goal we'd like to reach.
>

I might be confused, but I thought redumping referred to dumping using an
already dumped emacs.  I'm trying to bootstrap emacs with these additional
features loaded in the initial dump.

> Attempting to load email/rfc2047 produces an error to the effect that
> purecopy does not know how to purify a
> > char table (specifically a syntax table).
> > Is there a reason objects that aren't specifically recognized as being
> "purifiable" can't just be marked as
> > pinned like hash table without the purecopy attribute?  I mean, if I put
> that in the code, are there foreseeable
> > bugs that would result?
>
> Pure space will go away at some point, so we are unlikely to invest
> any effort into fixing this.
>

I recalled seeing an exchange to that effect on this list.   I'll try the
hack (on alloc.c) and see if it works as an interim solution.


Lynn

[-- Attachment #2: Type: text/html, Size: 2308 bytes --]