bug#20862: 25.0.50; 32-bit Emacs configured --with-wide-int miscompiles CL

[Paul Eggert <eggert@cs.ucla.edu>]

Eli Zaretskii wrote:

> Do you remember which Lisp file was being compiled when you got a core
> dump?

Sorry, no.  I don't think it matters -- if the garbage collector is bad anything 
can happen.

>  maybe the actual factor is the specific order
> in which the files are compiled (I bootstrap with "make -j8"),

Yes, that's plausible.

> Do you see something similar on your system?  How to go about
> debugging this?

I expect it'd require someone with expertise in byte-compiling.  It's not clear 
that it's a bug, other than a minor performance issue.  I do see something 
similar on my system.  The following files differed in one comparison I did:

cedet/semantic/grammar-wy.elc
cedet/semantic/wisent/javat-wy.elc
cedet/semantic/wisent/js-wy.elc
cedet/semantic/wisent/python-wy.elc
cedet/srecode/insert.elc
cedet/srecode/srt-wy.elc
gnus/auth-source.elc
gnus/message.elc
gnus/mm-decode.elc
org/ob-C.elc
progmodes/antlr-mode.elc
progmodes/cc-langs.elc
progmodes/cc-mode.elc
textmodes/rst.elc

In one case I looked at it appears to be gensym values, which ought to be OK.