public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/88173] `std::numeric_limits<T>::quiet_NaN()` is not always constexpr Date: Tue, 08 Dec 2020 18:52:39 +0000 [thread overview] Message-ID: <bug-88173-4-S5mp6lAae0@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 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2020-12-08 CC| |jason at gcc dot gnu.org --- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> --- Shorter: #define inf __builtin_huge_val() #define nan __builtin_nan("") constexpr bool b1 = inf > nan; // OK constexpr bool b2 = nan < inf; // ‘(+QNaN <= 1.7976931348623157e+308)’ is not a constant expression
next parent reply other threads:[~2020-12-08 18:52 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 ` jason at gcc dot gnu.org [this message] 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 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-S5mp6lAae0@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).