public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com> To: jason@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: debug/6436: dwarf2out ICE with typedef using attributes Date: Tue, 30 Apr 2002 10:56:00 -0000 [thread overview] Message-ID: <20020430175604.12403.qmail@sources.redhat.com> (raw) The following reply was made to PR debug/6436; it has been noted by GNATS. From: Jason Merrill <jason@redhat.com> To: Daniel Berlin <dberlin@dberlin.org> Cc: jakub@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <meissner@suse.de>, <gcc-gnats@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>, Mark Mitchell <mark@codesourcery.com>, Richard Sandiford <rsandifo@redhat.com> Subject: Re: debug/6436: dwarf2out ICE with typedef using attributes Date: Tue, 30 Apr 2002 18:48:33 +0100 --=-=-= >>>>> "Jason" == Jason Merrill <jason@redhat.com> writes: > One fix would be to not give the name 'A' to the anonymous struct. Thus. I've added Jakub's testcase to the testsuite as g++.dg/debug/typedef1.C. Booted and tested i686-pc-linux-gnu, applied trunk and 3.1. 2002-04-30 Jason Merrill <jason@redhat.com> * decl.c (grokdeclarator): Don't override TYPE_NAME of an anonymous class with a typedef if there are attributes. --=-=-= Content-Type: text/x-patch Content-Disposition: inline *** decl.c.~1~ Tue Apr 30 14:06:13 2002 --- decl.c Tue Apr 30 18:21:09 2002 *************** grokdeclarator (declarator, declspecs, d *** 11275,11280 **** --- 11275,11282 ---- && TYPE_NAME (type) && TREE_CODE (TYPE_NAME (type)) == TYPE_DECL && TYPE_ANONYMOUS_P (type) + /* Don't do this if there are attributes. */ + && (!attrlist || !*attrlist) && cp_type_quals (type) == TYPE_UNQUALIFIED) { tree oldname = TYPE_NAME (type); --=-=-=--
next reply other threads:[~2002-04-30 17:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-30 10:56 Jason Merrill [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-01 3:20 jason 2002-04-30 5:36 Jason Merrill 2002-04-29 11:36 Daniel Berlin 2002-04-29 10:56 Jason Merrill 2002-04-29 10:36 Daniel Berlin 2002-04-29 10:09 jason 2002-04-29 5:31 jakub
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=20020430175604.12403.qmail@sources.redhat.com \ --to=jason@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=jason@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).