Re: Skipping unexec via a big .elc file

[Ken Raeburn]

On Jan 21, 2017, at 02:58, Ken Raeburn <address@hidden> wrote:
> I built a couple versions, and found several .elc files different.  The first 
> case I looked at was macroexp--const-symbol-p in macroexp.elc.  From 
> disassembling, it appears that the expression “(boundp 
> 'byte-compile-const-variables)” is optimized out in the build from the branch 
> point, but not in the build including the dumped.elc changes.  I’m not sure 
> why yet, but it’s almost certainly a bug that they’re different.  And a bug 
> affecting the emacs-lisp environment and/or the byte compiler output could 
> certainly cause later attempts at byte compilation (using newly byte-compiled 
> code) to misbehave.

Ah, this may be a false alarm.  I’d overlooked the fact that the updated 
version (October 31) of Stefan’s patch changed that code to insert that 
expression on the branch, and I assumed the two were compiling the same source. 
 But if byte-compile-const-variables can be seen as unbound, that could also 
alter the optimization results compared to the master branch.  Perhaps that 
should be fixed, if possible.

Ken