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++/108566] [11/12/13 Regression] ICE: tree check: expected tree that contains 'decl with visibility' structure, have 'field_decl' in write_unqualified_name with anonymous struct inside an anonymous union since r11-2016-g6324c52bba490baa
Date: Fri, 10 Mar 2023 13:54:42 +0000 [thread overview]
Message-ID: <bug-108566-4-C6ZRsuN9uZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108566-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:e1c8cf9006bd278e969ab7ed35178067ce128f32
commit r13-6582-ge1c8cf9006bd278e969ab7ed35178067ce128f32
Author: Jason Merrill <jason@redhat.com>
Date: Thu Mar 9 23:33:43 2023 -0500
c++: class NTTP and nested anon union [PR108566]
We were failing to come up with the name for the anonymous union. It seems
like unfortunate redundancy, but the ABI does say that the name of an
anonymous union is its first named member.
PR c++/108566
gcc/cp/ChangeLog:
* mangle.cc (anon_aggr_naming_decl): New.
(write_unqualified_name): Use it.
gcc/testsuite/ChangeLog:
* g++.dg/abi/anon6.C: New test.
next prev parent reply other threads:[~2023-03-10 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 2:59 [Bug c++/108566] New: [11/12/13 Regression] ICE: tree check: expected tree that contains 'decl with visibility' structure, have 'field_decl' in write_unqualified_name, at cp/mangle.cc:1438 asolokha at gmx dot com
2023-01-27 3:16 ` [Bug c++/108566] " pinskia at gcc dot gnu.org
2023-01-27 3:19 ` [Bug c++/108566] ICE: tree check: expected tree that contains 'decl with visibility' structure, have 'field_decl' in write_unqualified_name with anonymous struct inside an anonymous union pinskia at gcc dot gnu.org
2023-01-27 3:21 ` pinskia at gcc dot gnu.org
2023-01-27 3:29 ` pinskia at gcc dot gnu.org
2023-02-06 13:51 ` [Bug c++/108566] [11/12/13 Regression] ICE: tree check: expected tree that contains 'decl with visibility' structure, have 'field_decl' in write_unqualified_name with anonymous struct inside an anonymous union since r11-2016-g6324c52bba490baa marxin at gcc dot gnu.org
2023-03-09 23:35 ` jason at gcc dot gnu.org
2023-03-10 3:28 ` jason at gcc dot gnu.org
2023-03-10 13:54 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-10 13:55 ` [Bug c++/108566] [11/12 " jason at gcc dot gnu.org
2023-03-15 10:01 ` rguenth at gcc dot gnu.org
2023-04-18 20:45 ` cvs-commit at gcc dot gnu.org
2023-05-29 10:07 ` [Bug c++/108566] [11 " jakub 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-108566-4-C6ZRsuN9uZ@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: link
Be 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).