public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/104389] [10/11/12 Regression] HUGE_VAL * 0.0 is no longer a NaN Date: Fri, 04 Feb 2022 19:19:28 +0000 [thread overview] Message-ID: <bug-104389-4-jVwPP1Psvu@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-02-04 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- double foo (void) { return __builtin_huge_val () * 0.0; } folds since r12-6959 to return 0.0 instead of return NAN; already in original dump.
next prev parent reply other threads:[~2022-02-04 19:19 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 [this message] 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 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-jVwPP1Psvu@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).