unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>, Rob Browning <rlb@defaultvalue.org>
Cc: gerd.moellmann@gmail.com, 57789@debbugs.gnu.org,
	Eli Zaretskii <eliz@gnu.org>
Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x
Date: Mon, 11 Sep 2023 11:08:13 -0700	[thread overview]
Message-ID: <CADwFkmkfHjoZUReHNqx6s6xq0ORy8q6wqJQdVWydD=shBWRNuQ@mail.gmail.com> (raw)
In-Reply-To: <yp1pm679dol.fsf@fencepost.gnu.org>

tags 57789 + moreinfo
thanks

Andrea Corallo <acorallo@gnu.org> writes:

> Rob Browning <rlb@defaultvalue.org> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>> Once you know which staticpro is being processed here, we'd need to
>>> examine its contents and try to figure out which parts cause the crash
>>> in GC.
>>
>> Thanks, and I'll try to look in to this further when I have time.  For
>> now I'm changing the debian packages to avoid native compilation on some
>> architectures (currently mips64el[1] and s390x).
>>
>> [1] There ./configure fails at the moment with "Error: -march=mips1 is
>>     not compatible with the selected ABI" when testing libgccjit.
>>     That's on eller.debian.org (mipsel host in a mips64el schroot).
>
> Hi Rob,
>
> any progress with this investigation?  Is the bug still reproducible
> with a recent codebase?

Ping.  Rob, any updates here?





  reply	other threads:[~2023-09-11 18:08 UTC|newest]

Thread overview: 21+ 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 [this message]
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='CADwFkmkfHjoZUReHNqx6s6xq0ORy8q6wqJQdVWydD=shBWRNuQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=57789@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=rlb@defaultvalue.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).