public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100995] New: Extend std::is_constant_evaluated in if warning Date: Wed, 09 Jun 2021 15:08:43 +0000 [thread overview] Message-ID: <bug-100995-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100995 Bug ID: 100995 Summary: Extend std::is_constant_evaluated in if warning Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mpolacek at gcc dot gnu.org Target Milestone: --- Let's extend the existing warning to detect more cases, as in http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p1938r3.html#compiler-warnings constexpr int f1() { if constexpr (!std::is_constant_evaluated() && sizeof(int) == 4) { // warning: always true return 0; } if (std::is_constant_evaluated()) { return 42; } else { if constexpr (std::is_constant_evaluated()) { // warning: always true return 0; } } return 7; } consteval int f2() { if (std::is_constant_evaluated() && f1()) { // warning: always true return 42; } return 7; } int f3() { if (std::is_constant_evaluated() && f1()) { // warning: always false return 42; } return 7; }
next reply other threads:[~2021-06-09 15:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-09 15:08 mpolacek at gcc dot gnu.org [this message] 2021-06-09 15:09 ` [Bug c++/100995] " mpolacek at gcc dot gnu.org 2021-06-09 16:09 ` jakub at gcc dot gnu.org 2021-06-11 2:32 ` cvs-commit at gcc dot gnu.org 2021-06-11 2:33 ` 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-100995-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).