public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103299] [11 Regression] accessing incorrect storage for designated init of anonymous union at constexpr context Date: Tue, 22 Mar 2022 05:18:07 +0000 [thread overview] Message-ID: <bug-103299-4-MxceIi4WQC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103299-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103299 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:2b2f575e6f27acc0c7ba6a3affc760bf2b96a84b commit r11-9678-g2b2f575e6f27acc0c7ba6a3affc760bf2b96a84b Author: Jason Merrill <jason@redhat.com> Date: Mon Mar 21 09:57:28 2022 -0400 c++: designated init and aggregate members [PR103337] Our C++20 designated initializer handling was broken with members of class type; we would find the relevant member and then try to find a member of the member with the same name. Or we would sometimes ignore the designator entirely. The former problem is fixed by the change to reshape_init_class, the latter by the change to reshape_init_r. PR c++/103337 PR c++/102740 PR c++/103299 PR c++/102538 gcc/cp/ChangeLog: * decl.c (reshape_init_class): Avoid looking for designator after we found it. (reshape_init_r): Keep looking for designator. gcc/testsuite/ChangeLog: * g++.dg/ext/flexary3.C: Remove one error. * g++.dg/parse/pr43765.C: Likewise. * g++.dg/cpp2a/desig22.C: New test. * g++.dg/cpp2a/desig23.C: New test. * g++.dg/cpp2a/desig24.C: New test. * g++.dg/cpp2a/desig25.C: New test.
next prev parent reply other threads:[~2022-03-22 5:18 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-17 9:08 [Bug c++/103299] New: accessing incorrect storage for " unlvsur at live dot com 2021-11-17 14:28 ` [Bug c++/103299] [10/11/12 Regression] accessing incorrect storage for designated init of anonymous " ppalka at gcc dot gnu.org 2021-11-17 14:37 ` [Bug c++/103299] [11/12 " ppalka at gcc dot gnu.org 2021-11-18 7:46 ` rguenth at gcc dot gnu.org 2021-11-19 17:17 ` ppalka at gcc dot gnu.org 2022-01-20 17:33 ` ppalka at gcc dot gnu.org 2022-03-18 19:17 ` jason at gcc dot gnu.org 2022-03-21 20:47 ` cvs-commit at gcc dot gnu.org 2022-03-21 21:01 ` [Bug c++/103299] [11 " jason at gcc dot gnu.org 2022-03-22 5:18 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-26 23:29 ` 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-103299-4-MxceIi4WQC@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).