public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/110305] Incorrect optimization with -O3 -fsignaling-nans -fno-signed-zeros
Date: Mon, 19 Jun 2023 17:53:22 +0000 [thread overview]
Message-ID: <bug-110305-4-QpKTKrpIuc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110305-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110305
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jeff Law <law@gcc.gnu.org>:
https://gcc.gnu.org/g:827b2a279fc6ad5bb76e4d2c2eb3432955b5e11c
commit r14-1952-g827b2a279fc6ad5bb76e4d2c2eb3432955b5e11c
Author: Toru Kisuki <tkisuki@tachyum.com>
Date: Mon Jun 19 11:51:09 2023 -0600
Do not allow "x + 0.0" to "x" optimization with -fsignaling-nans
gcc/
PR rtl-optimization/110305
* simplify-rtx.cc (simplify_context::simplify_binary_operation_1):
Handle HONOR_SNANS for x + 0.0.
next prev parent reply other threads:[~2023-06-19 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 6:08 [Bug c/110305] New: " tkisuki at tachyum dot com
2023-06-19 6:15 ` [Bug c/110305] " pinskia at gcc dot gnu.org
2023-06-19 6:50 ` tkisuki at tachyum dot com
2023-06-19 8:04 ` [Bug rtl-optimization/110305] " rguenth at gcc dot gnu.org
2023-06-19 10:34 ` tkisuki at tachyum dot com
2023-06-19 17:53 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-19 18:52 ` mmorrell at tachyum dot com
2023-06-19 20:07 ` pinskia at gcc dot gnu.org
2023-06-19 20:41 ` mmorrell at tachyum dot com
2023-06-20 21:46 ` mmorrell at tachyum dot com
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=bug-110305-4-QpKTKrpIuc@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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.
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).