public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gccbugbjorn at fahller dot se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110828] union constexpr dtor not constexpr when used in member array Date: Thu, 27 Jul 2023 16:25:19 +0000 [thread overview] Message-ID: <bug-110828-4-dSxpDJIa6L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110828-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110828 --- Comment #2 from Björn Fahller <gccbugbjorn at fahller dot se> --- If I write it in the same way in a function, it compiles. consteval auto f() { return S{}.f(); } constexpr auto b = f(); However, if I break it into a constexpr object S s; and return s.f(), it does not compile, this time because the construction of 's' fails because it refers to an unititialized variable, regardless of whether the member is an array or not. union type { constexpr type(){} constexpr ~type() {} int t; }; struct S { constexpr S() {} constexpr bool f() const { return true;} type v{}; }; consteval auto f() { constexpr S s; return s.f(); } constexpr auto b = f(); https://godbolt.org/z/68zY6ecxs
next prev parent reply other threads:[~2023-07-27 16:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-27 10:06 [Bug c++/110828] New: " gccbugbjorn at fahller dot se 2023-07-27 14:22 ` [Bug c++/110828] " ppalka at gcc dot gnu.org 2023-07-27 16:25 ` gccbugbjorn at fahller dot se [this message] 2023-07-27 17:54 ` 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-110828-4-dSxpDJIa6L@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).