From: Andrea Corallo <acorallo@gnu.org>
To: Pip Cet <pipcet@protonmail.com>
Cc: gerd.moellmann@gmail.com, 57789@debbugs.gnu.org,
Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>,
Rob Browning <rlb@defaultvalue.org>
Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x
Date: Wed, 08 Jan 2025 05:37:24 -0500 [thread overview]
Message-ID: <yp1ed1d4mmz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <871pxehguf.fsf@protonmail.com> (Pip Cet's message of "Tue, 07 Jan 2025 13:51:56 +0000")
Pip Cet <pipcet@protonmail.com> writes:
> "Rob Browning" <rlb@defaultvalue.org> writes:
>
>> Pip Cet <pipcet@protonmail.com> writes:
>>
>>> Same compiler? Is ASLR in use?
>>
>> Should be roughly the same compiler, both are building a "current"
>> unstable tree, and I build the one on zelenka a few days ago and the
>> mmdebstrap one the day before yesterday. Not sure offhand wrt ASLR.
>
> Hmm. Is there any way for you to share the binaries that don't work?
> It would be interesting to see whether the binary that crashes on
> silicon works in the emulator.
>
>>> In any case, I'm always interested in weird machines, even if they're
>>> virtual, so I'd appreciate such instructions.
>>
>> OK, so if you have access to a Debian host with recent enough versions
>> (fwiw, I was likely using trixie (testing) versions of debvm and
>> mmdebstrap), this should work.
>
> Thank you very much! The instructions worked for me!
>
> I could build Emacs, but, as expected, there was no crash.
>
> It's still possible that __builtin_unwind_init was buggy in one GCC
> version but not the other
Yep that's possible, but I had the impression that GCC middle-end was
(probably still is) buggy since forever on that 🤷
next prev parent reply other threads:[~2025-01-08 10:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 1:04 bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x Rob Browning
2022-09-14 2:42 ` Eli Zaretskii
2022-09-14 3:06 ` Rob Browning
2022-09-14 3:20 ` Rob Browning
2022-09-14 20:19 ` Rob Browning
2022-09-14 20:21 ` Rob Browning
2022-09-16 6:04 ` Gerd Möllmann
2022-09-17 21:04 ` Rob Browning
2022-09-18 5:22 ` Gerd Möllmann
2022-09-18 5:49 ` Eli Zaretskii
2022-09-18 5:55 ` Gerd Möllmann
2022-09-18 5:33 ` Eli Zaretskii
2022-09-24 21:06 ` Rob Browning
2023-06-07 21:15 ` Andrea Corallo
2023-09-11 18:08 ` Stefan Kangas
2025-01-02 1:07 ` Stefan Kangas
2025-01-02 3:40 ` Rob Browning
2025-01-02 5:04 ` Stefan Kangas
2025-01-03 18:34 ` Rob Browning
2025-01-03 18:57 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-05 19:18 ` Rob Browning
2025-01-07 13:51 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-08 10:37 ` Andrea Corallo [this message]
2025-01-03 18:59 ` Stefan Kangas
2025-01-05 19:23 ` Rob Browning
2022-09-15 7:10 ` Eli Zaretskii
2022-09-15 14:51 ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-15 16:26 ` Rob Browning
2022-09-16 8:43 ` Andrea Corallo
2022-09-16 8:39 ` Andrea Corallo
2022-09-17 21:00 ` Rob Browning
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=yp1ed1d4mmz.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=57789@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=pipcet@protonmail.com \
--cc=rlb@defaultvalue.org \
--cc=stefankangas@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).