unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 57789@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	Rob Browning <rlb@defaultvalue.org>
Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x
Date: Fri, 16 Sep 2022 08:43:37 +0000	[thread overview]
Message-ID: <xjfsfkrbtfq.fsf@ma.sdf.org> (raw)
In-Reply-To: <020828f9-c137-e584-89a5-f1ad0c38df9c@cs.ucla.edu> (Paul Eggert's message of "Thu, 15 Sep 2022 09:51:54 -0500")

Paul Eggert <eggert@cs.ucla.edu> writes:

> On 9/15/22 02:10, Eli Zaretskii wrote:
>>> Of course that's not remotely conclusive, but if all of the C code
>>> wasn't written with strict-aliasing in mind, then I wondered if it might
>>> make sense to consider adding -fno-strict-aliasing as a default option.
>> I don't know enough about this.  Perhaps Andrea or Paul could comment.
>>
> Throwing -fno-strict-aliasing in the mix is a bit like throwing -O1
> into the mix. I'm not surprised it would cause a Heisenbug to vanish;
> it doesn't mean strict aliasing is the problem.

Hi Paul,

totally agree with you.  The fact that even -g has an impact here
clearly shows that initial conditions are not necessary directly
connected with the final symptom we observe.

Best Regards

  Andrea





  parent reply	other threads:[~2022-09-16  8:43 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
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 [this message]
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=xjfsfkrbtfq.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=57789@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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).