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 middle-end/88173] constant folding of NaN comparison depends on order of operands Date: Tue, 08 Dec 2020 20:48:33 +0000 [thread overview] Message-ID: <bug-88173-4-pEN5JqLIjS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88173-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> --- What should be the exact rules for C++ floating point evaluation that trigger non-constant expressions? And shall that depend (like it partly does for GCC currently) on e.g. -ftrapping-math and other command line options? 1.0 / 0.0 - division by zero (for floating point results in Inf) 10000000000000.0 + 0.000000000000001 - inexact (hope this one not) inf - inf - invalid - non-NaN operands resulting in NaN result sqrt (-1) - likewise DBL_MAX * DBL_MAX - overflow DBL_MIN * DBL_MIN - underflow NaN + 1.0 - one or both operands NaN resulting in NaN sNaN + 1.0 - at least one operand sNaN
next prev parent reply other threads:[~2020-12-08 20:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88173-4@http.gcc.gnu.org/bugzilla/> 2020-12-08 18:52 ` [Bug c++/88173] `std::numeric_limits<T>::quiet_NaN()` is not always constexpr jason at gcc dot gnu.org 2020-12-08 19:47 ` [Bug middle-end/88173] constant folding of NaN comparison depends on order of operands jason at gcc dot gnu.org 2020-12-08 20:48 ` jakub at gcc dot gnu.org [this message] 2021-09-18 8:58 ` roger at nextmovesoftware dot com 2021-09-19 8:08 ` cvs-commit at gcc dot gnu.org 2021-09-19 21:42 ` roger at nextmovesoftware dot com 2021-11-08 10:01 ` pinskia at gcc dot gnu.org 2022-12-28 19:14 ` pinskia at gcc dot gnu.org
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-88173-4-pEN5JqLIjS@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).