Re: Loading tramp for dump goes into infinite regress

[Po Lu]

Lynn Winebarger <owinebar@gmail.com> writes:

> I'm not sure you can conclude that the benefit would be minor when the
> non-collected space is a 184MB dump file instead of a fixed pure space
> that is 2 or 2.4MB as it is in the standard pdump.

AFAIK we don't officially support any non-standard dump.

> At least some vestiges of the write barrier appear to be in place
> during dump mode.  I've had to make a lot of minor corrections of
> "defconst" keymaps to defvar, for example due to pure_write_error
> getting called.  Whether that barrier is uniformly enforced or not is
> one of the reasons I suspect this quick hack would not be sufficient.

I don't think it's very well enforced.  For example, any C code that
calls XSETCAR without checking whether or not the object (i.e. the reuse
argument to Fmatch_end) is writable will result in the invariant being
broken.