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 tree-optimization/104389] [10/11/12 Regression] HUGE_VAL * 0.0 is no longer a NaN Date: Sat, 05 Feb 2022 09:54:17 +0000 [thread overview] Message-ID: <bug-104389-4-0kX9I5NmNB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104389-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104389 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:b3763384a1f696260f3ee7bda8c0e7e4ad732ad9 commit r12-7072-gb3763384a1f696260f3ee7bda8c0e7e4ad732ad9 Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Feb 5 10:52:19 2022 +0100 match.pd: Fix x * 0.0 -> 0.0 folding [PR104389] The recent PR95115 change to punt in const_binop on folding operation with non-NaN operands into NaN if flag_trapping_math broke the following testcase, because the x * 0.0 simplification punts just if x maybe a NaN (because NaN * 0.0 is NaN not 0.0) or if one of the operands could be negative zero. But Inf * 0.0 or -Inf * 0.0 is also NaN, not 0.0, so when NaNs are honored we need to punt for possible infinities too. 2022-02-05 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/104389 * match.pd (x * 0 -> 0): Punt if x maybe infinite and NaNs are honored. * gcc.dg/pr104389.c: New test.
next prev parent reply other threads:[~2022-02-05 9:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-04 19:02 [Bug c/104389] New: " vstinner at redhat dot com 2022-02-04 19:15 ` [Bug c/104389] [10/11/12 Regression] " jakub at gcc dot gnu.org 2022-02-04 19:19 ` jakub at gcc dot gnu.org 2022-02-04 19:22 ` jakub at gcc dot gnu.org 2022-02-04 19:26 ` jakub at gcc dot gnu.org 2022-02-04 19:43 ` [Bug tree-optimization/104389] " jakub at gcc dot gnu.org 2022-02-04 22:28 ` glisse at gcc dot gnu.org 2022-02-05 9:54 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-05 10:22 ` [Bug tree-optimization/104389] [12 " jakub at gcc dot gnu.org 2022-02-07 7:15 ` xry111 at mengyan1223 dot wang
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-104389-4-0kX9I5NmNB@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).