From: Nick Clifton <nickc@redhat.com>
To: Kao Dome <kaodome@icloud.com>, binutils@sourceware.org
Subject: Re: LTO seems to change the outcome of the division by zero raises SIGFPE test.
Date: Tue, 26 Jul 2022 14:49:11 +0100 [thread overview]
Message-ID: <d0e6e331-8010-78fb-1614-80efa2310232@redhat.com> (raw)
In-Reply-To: <2f6b659b-79a1-489f-a28a-bc5d5ae5e885@me.com>
Hi Kao,
> When CFLAGS include a flavor of LTO, for example, "-flto", executing the binary leads to a
> return value of 1, but it exists through the one at end of the program, *not* the signal
> handler. When no LTO is used, executing returns 0.
I am pretty sure that this is a gcc issue, rather than a binutils one. When LTO
is enabled the compiler is invoked twice, and it would be my guess that it is this
second invocation which is changing the behaviour of the final program.
This could be a known issue. I suggest that you check to see which version of gcc
you are using, and if it is not the latest, upgrade. If the problem persists then
please file a bug report with the gcc bugzilla system.
Cheers
Nick
prev parent reply other threads:[~2022-07-26 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 16:58 Kao Dome
2022-07-26 13:49 ` Nick Clifton [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d0e6e331-8010-78fb-1614-80efa2310232@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=kaodome@icloud.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.
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).