public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97665] New: constexpr union array member incorrectly rejected as non-constexpr Date: Sun, 01 Nov 2020 17:29:54 +0000 [thread overview] Message-ID: <bug-97665-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97665 Bug ID: 97665 Summary: constexpr union array member incorrectly rejected as non-constexpr Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ldalessandro at gmail dot com Target Milestone: --- GCC currently rejects the following code snippet, where it infers the constexpr definition of V as non-constexpr. The monostate member provides a temporary workaround. https://godbolt.org/z/Ph1n1P ``` struct Foo { constexpr Foo() {} }; union U { // struct {} monostate = {}; Foo foo; constexpr U() {} }; struct V { U storage[1]; }; constexpr V v; ```
next reply other threads:[~2020-11-01 17:29 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-01 17:29 ldalessandro at gmail dot com [this message] 2020-11-01 17:31 ` [Bug c++/97665] " ldalessandro at gmail dot com 2020-11-02 11:55 ` jakub at gcc dot gnu.org 2020-11-02 12:24 ` jakub at gcc dot gnu.org 2020-11-02 17:30 ` ldalessandro at gmail dot com 2020-11-02 17:37 ` ldalessandro at gmail dot com 2020-11-02 17:42 ` jakub at gcc dot gnu.org 2020-11-02 17:49 ` ldalessandro at gmail dot com 2021-08-04 17:06 ` pinskia at gcc dot gnu.org 2021-09-01 21:12 ` pinskia at gcc dot gnu.org 2022-11-22 7:37 ` dysnomia.eris at online dot de 2022-11-23 2:17 ` de34 at live dot cn 2023-06-14 4:02 ` pinskia 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-97665-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).