public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dodji at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/47510] DW_TAG_typedef can have children when designating a naming typedef
Date: Wed, 16 Mar 2011 21:33:00 -0000 [thread overview]
Message-ID: <bug-47510-4-Fk2UsVCOIL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47510-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47510
Dodji Seketeli <dodji at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2011.03.16 21:30:27
Summary|[4.6/4.7 Regression] |DW_TAG_typedef can have
|DW_TAG_typedef can have |children when designating a
|children when designating a |naming typedef
|naming typedef |
Ever Confirmed|0 |1
--- Comment #9 from Dodji Seketeli <dodji at gcc dot gnu.org> 2011-03-16 21:30:27 UTC ---
The initial issue has been fixed in trunk (4.7) and 4.6 so far. There
are two tangent issues that remain, though. One is the template
related case raised by Jan in comment #3, and the other one is that
constructors of the anonymous struct are named t. They should also be
anonymous and have DW_AT_linkage_name set to t. This is from a
comment Jason made at
http://gcc.gnu.org/ml/gcc-patches/2011-03/msg00926.html. So I am
keeping this bug open to track these. I will maybe open separate bugs
for these issues at some point.
next prev parent reply other threads:[~2011-03-16 21:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 11:42 [Bug debug/47510] New: " dodji at gcc dot gnu.org
2011-01-28 12:01 ` [Bug debug/47510] " dodji at gcc dot gnu.org
2011-01-28 17:02 ` dodji at gcc dot gnu.org
2011-02-03 15:21 ` jan.kratochvil at redhat dot com
2011-03-14 21:03 ` dodji at gcc dot gnu.org
2011-03-15 16:29 ` rguenth at gcc dot gnu.org
2011-03-16 10:25 ` dodji at gcc dot gnu.org
2011-03-16 20:19 ` [Bug debug/47510] [4.6/4.7 Regression] " dodji at gcc dot gnu.org
2011-03-16 21:11 ` dodji at gcc dot gnu.org
2011-03-16 21:19 ` dodji at gcc dot gnu.org
2011-03-16 21:33 ` dodji at gcc dot gnu.org [this message]
2011-03-17 11:34 ` [Bug debug/47510] [4.6 " dodji at gcc dot gnu.org
2011-03-17 16:53 ` dodji at gcc dot gnu.org
2011-03-25 19:57 ` [Bug debug/47510] " jakub at gcc dot gnu.org
2011-04-14 8:14 ` dodji at gcc dot gnu.org
2011-04-14 8:28 ` jan.kratochvil at redhat dot com
2011-04-28 16:19 ` rguenth at gcc dot gnu.org
2011-10-10 13:48 ` daniel_beichl at gmx dot net
2012-03-04 18:31 ` eu at doxos dot eu
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-47510-4-Fk2UsVCOIL@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).