public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/103406] gcc -O0 behaves differently on "DBL_MAX related operations" than gcc -O1 and above Date: Thu, 25 Nov 2021 20:29:10 +0000 [thread overview] Message-ID: <bug-103406-4-4aYSL7rlK6@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 #14 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- There is no reasonable definition of how operands of binary + map to particular operands of a particular instruction and so no -f or -m option could sensibly be defined for that. When the result is a NaN, there is no requirement at all on what (quiet) NaN it is (beyond a preference for preservation of the payload of a NaN operand if there is at least one NaN operand).
next prev parent reply other threads:[~2021-11-25 20:29 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 2021-11-25 19:40 ` [Bug middle-end/103406] " roger at nextmovesoftware dot com 2021-11-25 20:29 ` joseph at codesourcery dot com [this message] 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-4aYSL7rlK6@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).