From: Eli Zaretskii <eliz@gnu.org>
To: akrl@sdf.org
Cc: schwab@linux-m68k.org, 50230@debbugs.gnu.org
Subject: bug#50230: Endian problem with native compilation
Date: Sat, 04 Sep 2021 12:15:24 +0300 [thread overview]
Message-ID: <83pmtowvkj.fsf@gnu.org> (raw)
In-Reply-To: <83y28gp9gb.fsf@gnu.org> (message from Eli Zaretskii on Wed, 01 Sep 2021 19:05:56 +0300)
> Date: Wed, 01 Sep 2021 19:05:56 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: schwab@linux-m68k.org, 50230@debbugs.gnu.org
>
> > From: Andrea Corallo <akrl@sdf.org>
> > Cc: schwab@linux-m68k.org, 50230@debbugs.gnu.org
> > Date: Wed, 01 Sep 2021 15:13:54 +0000
> >
> > This is changing the cast functions we synthesize and use in all the
> > code we generate, so yes it is potentially destabilizing.
> >
> > That said the generated code looks correct to me (and considerably
> > cleaner). Also, given these functions are really the foundation of a
> > lot of other code we generate I guess would be unlikely to have these
> > wrong but still have the testsuite passing clean and Emacs booting up
> > correctly. Call me optimistic but I'd be pretty confident with this
> > change...
>
> OK, thanks. We'll see how it goes (after you find the problem with
> endianness and fix it).
I've noticed that building Emacs --with-native-compilation after this
change still uses the same subdirectory of native-lisp/ for the
preloaded files, and doesn't recompile *.eln files that were
native-compiled before the change (unless the corresponding *.el files
were updated in the meantime). Shouldn't we recompile all the *.eln
files after this change?
I don't know if Andreas did recompile all of them, but if not, perhaps
that's one reason why the change didn't fix Emacs on big-endian
systems?
next prev parent reply other threads:[~2021-09-04 9:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 17:39 bug#50230: Endian problem with native compilation Andreas Schwab
2021-08-30 9:54 ` Andreas Schwab
2021-08-30 13:03 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-30 13:13 ` Andreas Schwab
2021-08-30 13:20 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-01 12:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-01 13:19 ` Andreas Schwab
2021-09-01 14:00 ` Eli Zaretskii
2021-09-01 15:13 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-01 16:05 ` Eli Zaretskii
2021-09-04 9:15 ` Eli Zaretskii [this message]
2021-09-04 9:25 ` Andreas Schwab
2021-09-04 9:45 ` Eli Zaretskii
2021-09-04 9:49 ` Andreas Schwab
2021-09-04 10:06 ` Eli Zaretskii
2021-09-04 11:01 ` Andreas Schwab
2021-09-04 11:06 ` Eli Zaretskii
2021-11-30 17:02 ` Andrea Corallo
2021-11-30 17:06 ` Andreas Schwab
2021-11-30 17:10 ` Andrea Corallo
2021-11-30 21:05 ` Andreas Schwab
2021-12-01 3:19 ` Eli Zaretskii
2022-08-22 14:47 ` Lars Ingebrigtsen
2022-09-19 19:18 ` Lars Ingebrigtsen
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=83pmtowvkj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50230@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=schwab@linux-m68k.org \
/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).