public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111132] New: Function redeclaration in local scope breaks constant expression evaluation Date: Thu, 24 Aug 2023 12:54:54 +0000 [thread overview] Message-ID: <bug-111132-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111132 Bug ID: 111132 Summary: Function redeclaration in local scope breaks constant expression evaluation Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fchelnokov at gmail dot com Target Milestone: --- This program constexpr bool bar(void) { return true; } constexpr bool foo() { constexpr bool bar(void); return bar(); } static_assert( foo() ); is accepted in Clang, but not in GCC, which prints error: non-constant condition for static assertion 10 | static_assert( foo() ); | ~~~^~ <source>:10:19: in 'constexpr' expansion of 'foo()' <source>:7:15: error: 'constexpr bool bar()' used before its definition 7 | return bar(); | ~~~^~ Online demo: https://godbolt.org/z/3PvoEx61x
next reply other threads:[~2023-08-24 12:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-24 12:54 fchelnokov at gmail dot com [this message] 2023-08-24 18:29 ` [Bug c++/111132] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-08-24 19:54 ` ppalka at gcc dot gnu.org 2023-10-17 10:27 ` rguenth at gcc dot gnu.org 2024-03-07 23:23 ` law at gcc dot gnu.org 2024-04-01 23:18 ` mpolacek at gcc dot gnu.org 2024-04-05 13:11 ` cvs-commit at gcc dot gnu.org 2024-04-05 13:26 ` [Bug c++/111132] [11/12/13 " 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-111132-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).