From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: schwab@linux-m68k.org, 50230@debbugs.gnu.org
Subject: bug#50230: Endian problem with native compilation
Date: Wed, 01 Sep 2021 15:13:54 +0000 [thread overview]
Message-ID: <xjfo89c1g7h.fsf@ma.sdf.org> (raw)
In-Reply-To: <838s0gqtu4.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 01 Sep 2021 17:00:19 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 50230@debbugs.gnu.org
>> Date: Wed, 01 Sep 2021 12:28:59 +0000
>> From: Andrea Corallo via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>
>> > define_cast_functions contains all the horrible mess.
>> >
>> > Andreas.
>>
>> Hi Andreas,
>>
>> is this bug fixed with 6767e5565?
>
> Andrea,
>
> Regardless of whether the big-endian bugs are solved with this, could
> you please try to give us an idea of how this change could affect the
> native code produced by Emacs, and whether it could destabilize Emacs
> with natively-compiled Lisp code to any significant degree?
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...
Not sure I can say more than this, hope it helps.
Regards
Andrea
next prev parent reply other threads:[~2021-09-01 15:13 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 [this message]
2021-09-01 16:05 ` Eli Zaretskii
2021-09-04 9:15 ` Eli Zaretskii
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=xjfo89c1g7h.fsf@ma.sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=50230@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.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).