From: Eli Zaretskii <eliz@gnu.org>
To: pipcet@gmail.com
Cc: mwd@md5i.com, monnier@iro.umontreal.ca, 46502@debbugs.gnu.org,
akrl@sdf.org
Subject: bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure
Date: Sat, 20 Feb 2021 13:48:33 +0200 [thread overview]
Message-ID: <83zgzzyn72.fsf@gnu.org> (raw)
In-Reply-To: <831rdb0yt9.fsf@gnu.org> (message from Eli Zaretskii on Sat, 20 Feb 2021 13:21:38 +0200)
> Date: Sat, 20 Feb 2021 13:21:38 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: mwd@md5i.com, 46502@debbugs.gnu.org, akrl@sdf.org
>
> > 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?
Btw, if you let macroexp.el byte-compile uninterrupted, then rename
the .elc file and re-compile the .el file, do you get identical .elc
files?
next prev parent reply other threads:[~2021-02-20 11:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 5:05 bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure Michael Welsh Duggan
2021-02-18 9:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 10:14 ` Pip Cet
2021-02-18 10:29 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 14:34 ` Eli Zaretskii
2021-02-19 13:31 ` Pip Cet
2021-02-19 13:48 ` Eli Zaretskii
2021-02-19 14:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-20 4:35 ` Pip Cet
2021-02-20 8:56 ` Eli Zaretskii
2021-02-20 9:15 ` Pip Cet
2021-02-20 11:21 ` Eli Zaretskii
2021-02-20 11:48 ` Eli Zaretskii [this message]
2021-02-20 12:03 ` Pip Cet
2021-02-20 12:42 ` Eli Zaretskii
2021-02-20 17:00 ` Pip Cet
2021-02-20 17:18 ` Eli Zaretskii
2021-02-20 15:42 ` Stefan Monnier
2021-02-20 17:02 ` Pip Cet
2021-02-20 17:12 ` Stefan Monnier
[not found] ` <jwvo8etr7hf.fsf-monnier+emacs@gnu.org>
2021-04-05 2:56 ` Michael Welsh Duggan
2021-02-18 14:55 ` Michael Welsh Duggan
2021-02-18 15:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zgzzyn72.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46502@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=monnier@iro.umontreal.ca \
--cc=mwd@md5i.com \
--cc=pipcet@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).