public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bekenn at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105321] New: "non-constant condition" issued for function containing a short-circuited unevaluated non-constant expression Date: Wed, 20 Apr 2022 18:47:32 +0000 [thread overview] Message-ID: <bug-105321-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105321 Bug ID: 105321 Summary: "non-constant condition" issued for function containing a short-circuited unevaluated non-constant expression Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: bekenn at gmail dot com Target Milestone: --- bool handle_error(); constexpr int echo(int value, bool yes = true) noexcept { return (yes || handle_error()), value; } static_assert(echo(10) == 10, ""); --- <source>:8:24: error: non-constant condition for static assertion 8 | static_assert(echo(10) == 10, ""); | ~~~~~~~~~^~~~~ <source>:8:19: in 'constexpr' expansion of 'echo(10, 1)' <source>:3:36: error: 'yes' is not a constant expression 3 | constexpr int echo(int value, bool yes = true) noexcept | ~~~~~^~~~~~~~~~ https://godbolt.org/z/vsd9xdW5c --- It appears that the || operator isn't short-circuiting correctly during constant evaluation. This seems to be very particular; if I replace `yes` with a more complicated expression (such as `!no`), the problem disappears. This issue shows up in every version of GCC I've tried, including 11.2 and the current "trunk" release on Compiler Explorer.
next reply other threads:[~2022-04-20 18:47 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-20 18:47 bekenn at gmail dot com [this message] 2022-04-20 19:10 ` [Bug c++/105321] " mpolacek at gcc dot gnu.org 2022-04-20 19:45 ` mpolacek at gcc dot gnu.org 2022-04-20 19:48 ` mpolacek at gcc dot gnu.org 2022-04-20 19:55 ` mpolacek at gcc dot gnu.org 2022-04-20 19:59 ` [Bug c++/105321] [9/10/11/12 Regression] " mpolacek at gcc dot gnu.org 2022-04-21 14:18 ` cvs-commit at gcc dot gnu.org 2022-04-21 15:39 ` [Bug c++/105321] [9/10/11 " mpolacek at gcc dot gnu.org 2022-04-21 17:00 ` bekenn at gmail dot com 2022-04-22 21:01 ` cvs-commit at gcc dot gnu.org 2022-04-22 21:01 ` mpolacek 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-105321-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).