public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gnu at nemanjaboric dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/98829] Different results with -O3 and custom quiet NaN Date: Mon, 25 Jan 2021 23:18:10 +0000 [thread overview] Message-ID: <bug-98829-4-wPJ7GWXnwA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98829-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98829 --- Comment #3 from Nemanja Boric <gnu at nemanjaboric dot com> --- Changing: static constexpr std::uint64_t kMagicNumber = 1730; static constexpr std::uint64_t kCustomNaN = 0x7ff0000000000000 | kMagicNumber; to static inline std::uint64_t kMagicNumber = 1730; static inline std::uint64_t kCustomNaN = 0x7ff0000000000000 | kMagicNumber; also avoids the issue.
next prev parent reply other threads:[~2021-01-25 23:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-25 22:32 [Bug c++/98829] New: " gnu at nemanjaboric dot com 2021-01-25 22:55 ` [Bug middle-end/98829] " pinskia at gcc dot gnu.org 2021-01-25 22:59 ` gnu at nemanjaboric dot com 2021-01-25 23:18 ` gnu at nemanjaboric dot com [this message] 2021-01-26 8:20 ` rguenth at gcc dot gnu.org 2021-01-26 11:02 ` gnu at nemanjaboric dot com 2021-01-27 16:42 ` jakub at gcc dot gnu.org 2022-01-26 14:59 ` nemanjab at amazon 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-98829-4-wPJ7GWXnwA@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).