public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pdimov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104426] New: -fsanitize=undefined causes constexpr failures Date: Mon, 07 Feb 2022 17:46:46 +0000 [thread overview] Message-ID: <bug-104426-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104426 Bug ID: 104426 Summary: -fsanitize=undefined causes constexpr failures Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pdimov at gmail dot com Target Milestone: --- The following program ``` struct category { constexpr bool failed() const noexcept { return true; } }; inline constexpr category s_cat; struct condition { category const* cat_; constexpr bool failed() const noexcept { if( cat_ ) { return cat_->failed(); } else { return false; } } }; int main() { constexpr condition cond{ &s_cat }; static_assert( cond.failed() ); } ``` compiles without -fsanitize=undefined (https://godbolt.org/z/Pn9M5ocfz), but fails with it (https://godbolt.org/z/KKc8Tb9qe) with ``` <source>: In function 'int main()': <source>:31:31: error: non-constant condition for static assertion 31 | static_assert( cond.failed() ); | ~~~~~~~~~~~^~ <source>:31:31: in 'constexpr' expansion of 'cond.condition::failed()' <source>:17:13: error: '((& s_cat) != 0)' is not a constant expression 17 | if( cat_ ) | ^~~~ ``` This happens under all GCC versions starting from 7. (The above is an extract from the test suite for boost::system::error_condition.)
next reply other threads:[~2022-02-07 17:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-07 17:46 pdimov at gmail dot com [this message] 2022-02-07 21:14 ` [Bug c++/104426] " redi at gcc dot gnu.org 2022-02-07 21:15 ` redi at gcc dot gnu.org 2022-02-07 21:17 ` jakub at gcc dot gnu.org 2022-02-07 21:29 ` pdimov at gmail dot com 2022-02-08 9:01 ` rguenth at gcc dot gnu.org 2022-02-08 10:52 ` jakub at gcc dot gnu.org 2024-05-15 9:08 ` redi 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-104426-4@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).