public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105622] New: ICE in cxx_eval_store_expression with [[no_unique_address]] and empty data members Date: Mon, 16 May 2022 19:06:50 +0000 [thread overview] Message-ID: <bug-105622-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105622 Bug ID: 105622 Summary: ICE in cxx_eval_store_expression with [[no_unique_address]] and empty data members Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ppalka at gcc dot gnu.org Target Milestone: --- struct empty { empty() = default; constexpr empty(int) { } }; struct container { empty __begin_ = {}; [[no_unique_address]] empty __size_ = 0; }; constexpr bool test() { container s; return true; } static_assert(test()); testcase.ii: In function ‘constexpr bool test()’: testcase.ii:12:13: in ‘constexpr’ expansion of ‘s.container::container()’ testcase.ii:12:13: internal compiler error: in cxx_eval_store_expression, at cp/constexpr.cc:5927 12 | container s; | ^ 0x6a0ca0 cxx_eval_store_expression /home/patrick/gcc/gcc/cp/constexpr.cc:5927 0x96c254 cxx_eval_constant_expression /home/patrick/gcc/gcc/cp/constexpr.cc:6847 0x96c4d6 cxx_eval_constant_expression /home/patrick/gcc/gcc/cp/constexpr.cc:7236 0x96c717 cxx_eval_constant_expression /home/patrick/gcc/gcc/cp/constexpr.cc:7048
next reply other threads:[~2022-05-16 19:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-16 19:06 ppalka at gcc dot gnu.org [this message] 2022-05-16 19:08 ` [Bug c++/105622] [13 Regression] ICE in cxx_eval_store_expression with [[no_unique_address]] and empty data members since r13-160-g967cdbe6629653 ppalka at gcc dot gnu.org 2022-05-17 6:58 ` [Bug c++/105622] [13 Regression] ICE in cxx_eval_store_expression with [[no_unique_address]] " rguenth at gcc dot gnu.org 2022-05-17 22:16 ` jason at gcc dot gnu.org 2022-05-24 19:50 ` cvs-commit at gcc dot gnu.org 2022-05-24 20:07 ` jason 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-105622-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).