bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure

[Eli Zaretskii]

> From: Pip Cet <pipcet@gmail.com>
> Date: Sat, 20 Feb 2021 09:15:48 +0000
> Cc: akrl@sdf.org, mwd@md5i.com, 46502@debbugs.gnu.org
> 
> > Can you send the diffs as an attachment?
> 
> I'm sending the complete diff, even though it's a bit large... The
> path differences are obviously okay, and I'm not going to complain
> about differences in gensym numbering, but byte-optimize-lapcode, to
> pick an example at random, differs in the bytecode.

Thanks.  Stefan, any idea why we see differences here?

> > And when exactly did you interrupt the second run?  The first things
> > that get compiled are these:
> >
> >   COMPILE_FIRST = \
> >           $(lisp)/emacs-lisp/macroexp.elc \
> 
> HERE
> 
> >           $(lisp)/emacs-lisp/cconv.elc    \
> >           $(lisp)/emacs-lisp/byte-opt.elc \
> >           $(lisp)/emacs-lisp/bytecomp.elc \
> >           $(lisp)/emacs-lisp/autoload.elc
> >
> > Which one of these was being compiled when you pressed Ctrl-C?
> 
> cconv.el, after macroexp.el had been compiled successfully.

So it's possible that in one case the compilation used some of these
files in .elc form, while in the other case they were used in .el
form?

> > > So we should delete the early-compilation .elcs if we end up deleting
> > > bootstrap-emacs.pdmp, too?
> >
> > No, I don't think so.  (What is the relation between
> > bootstrap-emacs.pdmp and the produced *.elc files?)
> 
> A circular one. bootstrap-emacs.pdmp includes status derived from the
> .elc files if those are present before the dump, and it is used to
> generate the .elc files otherwise.

If the differences between the .elc files don't exist, or are
innocent, this doesn't matter, does it?  It's the same as when the
compiler injects the timestamp of the compilation into the object
files it produces.