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 middle-end/103406] [12 Regression] gcc -O0 behaves differently on "DBL_MAX related operations" than gcc -O1 and above Date: Thu, 25 Nov 2021 19:04:05 +0000 [thread overview] Message-ID: <bug-103406-4-mnPMioHedt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103406-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103406 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>: https://gcc.gnu.org/g:6ea5fb3cc7f3cc9b731d72183c66c23543876f5a commit r12-5529-g6ea5fb3cc7f3cc9b731d72183c66c23543876f5a Author: Roger Sayle <roger@nextmovesoftware.com> Date: Thu Nov 25 19:02:06 2021 +0000 PR middle-end/103406: Check for Inf before simplifying x-x. This is a simple one line fix to the regression PR middle-end/103406, where x - x is being folded to 0.0 even when x is +Inf or -Inf. In GCC 11 and previously, we'd check whether the type honored NaNs (which implicitly covered the case where the type honors infinities), but my patch to test whether the operand could potentially be NaN failed to also check whether the operand could potentially be Inf. 2021-11-25 Roger Sayle <roger@nextmovesoftware.com> gcc/ChangeLog PR middle-end/103406 * match.pd (minus @0 @0): Check tree_expr_maybe_infinite_p. gcc/testsuite/ChangeLog PR middle-end/103406 * gcc.dg/pr103406.c: New test case.
next prev parent reply other threads:[~2021-11-25 19:04 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-24 11:09 [Bug c/103406] New: " shaohua.li at inf dot ethz.ch 2021-11-24 11:21 ` [Bug c/103406] " pinskia at gcc dot gnu.org 2021-11-24 11:23 ` ubizjak at gmail dot com 2021-11-24 11:29 ` pinskia at gcc dot gnu.org 2021-11-24 11:54 ` rguenth at gcc dot gnu.org 2021-11-24 12:01 ` rguenth at gcc dot gnu.org 2021-11-24 12:02 ` rguenth at gcc dot gnu.org 2021-11-24 12:03 ` [Bug middle-end/103406] [12 Regression] " rguenth at gcc dot gnu.org 2021-11-24 12:29 ` roger at nextmovesoftware dot com 2021-11-24 13:02 ` rguenth at gcc dot gnu.org 2021-11-24 13:04 ` rguenth at gcc dot gnu.org 2021-11-24 13:05 ` rguenth at gcc dot gnu.org 2021-11-24 22:22 ` joseph at codesourcery dot com 2021-11-25 19:04 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-25 19:40 ` [Bug middle-end/103406] " roger at nextmovesoftware dot com 2021-11-25 20:29 ` joseph at codesourcery dot com 2021-11-26 17:58 ` roger at nextmovesoftware 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-103406-4-mnPMioHedt@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: linkBe 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).