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++/105925] [11/12/13 Regression] Could not convert '{{0, 0.0}}' from '<brace-enclosed initializer list>' to 'X' since r12-954-g84fd1b5dff70cd74 Date: Thu, 23 Jun 2022 21:16:43 +0000 [thread overview] Message-ID: <bug-105925-4-7gn3QRonBh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105925-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105925 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:d610ae121e8ecd738de4dc01e6ac11ecf7c2327e commit r13-1226-gd610ae121e8ecd738de4dc01e6ac11ecf7c2327e Author: Jason Merrill <jason@redhat.com> Date: Thu Jun 23 16:04:02 2022 -0400 c++: anon union designated init [PR105925] This testcase was failing because CONSTRUCTOR_IS_DESIGNATED_INIT wasn't getting set on the introduced CONSTRUCTOR for the anonymous union, and build_aggr_conv uses that flag to decide whether to pay attention to the indexes of the CONSTRUCTOR. So set the flag when we see a designator rather than relying on copying it from another CONSTRUCTOR. This avoids some redundant errors on desig4.C because we stop setting CONSTRUCTOR_IS_DESIGNATED_INIT on _Complex CONSTRUCTORs where it's nonsense. PR c++/105925 gcc/cp/ChangeLog: * decl.cc (reshape_init_array_1): Set CONSTRUCTOR_IS_DESIGNATED_INIT here. (reshape_init_class): And here. (reshape_init): Not here. gcc/testsuite/ChangeLog: * g++.dg/ext/desig4.C: Remove extra errors. * g++.dg/cpp2a/desig26.C: New test.
next prev parent reply other threads:[~2022-06-23 21:16 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-11 8:53 [Bug c++/105925] New: [11.1 Regression] Could not convert '{{0, 0.0}}' from '<brace-enclosed initializer list>' to 'X' jehova at existiert dot net 2022-06-11 12:59 ` [Bug c++/105925] [11/12 " redi at gcc dot gnu.org 2022-06-16 13:23 ` [Bug c++/105925] [11/12/13 " marxin at gcc dot gnu.org 2022-06-16 13:23 ` marxin at gcc dot gnu.org 2022-06-16 13:24 ` [Bug c++/105925] [11/12/13 Regression] Could not convert '{{0, 0.0}}' from '<brace-enclosed initializer list>' to 'X' since r12-954-g84fd1b5dff70cd74 marxin at gcc dot gnu.org 2022-06-23 15:42 ` jason at gcc dot gnu.org 2022-06-23 21:16 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-23 21:17 ` cvs-commit at gcc dot gnu.org 2022-06-23 21:38 ` cvs-commit at gcc dot gnu.org 2022-06-24 0:45 ` cvs-commit at gcc dot gnu.org 2022-06-24 0:46 ` 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-105925-4-7gn3QRonBh@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).