Re: Unmark pdumped objects
>>>> "OG" == Olivier Galibert
<galibert(a)pobox.com> writes:
OG> On Mon, Oct 25, 1999 at 10:31:08AM -0700, Martin Buchholz wrote:
> I believe that when I implemented this, dumped compiled function
> objects had already had optimize_compiled_function called for them
> prior to dumping. So only functions read into the executable image at
> runtime would be lazily optimized.
OG> This is not, though, what is happening right now. I don't think I
OG> touched anything in that area, though.
OG> OG.
I note that optimize_compiled_function() is declared in bytecode.h,
yet only used in bytecode.c. I am so incredibly pedantic that this is
a good sign that optimize_compiled_function() *used* to be called in
some other C file. Check out a pre-pdump version of XEmacs, circa
Feb. 1999, and I think you'll find that reading in a compiled_function
object would always optimize it if about to dump, probably in alloc.c,
perhaps in make-byte-code.
Martin