On Mon, Oct 25, 1999 at 07:17:01PM -0700, Martin Buchholz wrote:
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.
I'm impressed.
DEFUN ("make-byte-code", Fmake_byte_code, 4, MANY, 0, /*
[...]
if (purify_flag)
{
[...]
optimize_compiled_function (fun);
bump_purestat (&purestat_opaque_instructions,
pure_sizeof (f->instructions));
}
Here is the commit:
1.42.2.9 Thu Apr 22 7:27:14 1999 by hrvojen
Branch: release-21-2
Diffs to 1.42.2.8
Committed Olivier's mega patch from <19990405154713.A41774(a)frodo.loria.fr>.
Hence it has gone with my killer blow on the purespace code. Well, I
don't think I have a "in the dumping" flag handy enymore, but it is
easy enough to add. Hvroje seems to think that the space expansion
due to the systematic use of o-c-f may be a problem, though.
Comments?
OG.