public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dodji at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/44188] Fails to produce DW_AT_typedef for typedef of anonymous struct
Date: Thu, 27 May 2010 19:30:00 -0000	[thread overview]
Message-ID: <20100527193017.10128.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44188-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from dodji at gcc dot gnu dot org  2010-05-27 19:30 -------
Subject: Bug 44188

Author: dodji
Date: Thu May 27 19:29:53 2010
New Revision: 159943

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159943
Log:
Fix PR c++/44188

gcc/ChangeLog:
        PR c++/44188
        * c-common.c (is_typedef_decl): Move this definition ...
        * tree.c (is_typedef_decl): ... here.
        (typdef_variant_p): Move definition here from gcc/cp/tree.c.
        * c-common.h (is_typedef_decl): Move this declaration ...
        * tree.h (is_typedef_decl): ... here.
        (typedef_variant_p): Move declaration here from gcc/cp/cp-tree.h
        * dwarf2out.c (is_naming_typedef_decl): New function.
        (gen_tagged_type_die): Split out of ...
        (gen_type_die_with_usage): ... this function. When an anonymous
        tagged type is named by a typedef, make sure a DW_TAG_typedef DIE
        is emitted for the typedef.
        (gen_typedef_die): Emit DW_TAG_typedef also for typedefs naming
        anonymous tagged types.

gcc/cp/ChangeLog:
        PR c++/44188
        * cp-tree.h (typedef_variant_p): Move this declaration to
        gcc/tree.h.
        * tree.c (typedef_variant_p): Move this definition to gcc/tree.c.
        * decl.c (grokdeclarator): Do not rename debug info of an
        anonymous tagged type named by a typedef.

gcc/testsuite/ChangeLog:
        PR c++/44188
        * g++.dg/debug/dwarf2/typedef3.C: New test.

Added:
    trunk/gcc/testsuite/g++.dg/debug/dwarf2/typedef3.C
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/c-common.c
    trunk/gcc/c-common.h
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/cp-tree.h
    trunk/gcc/cp/decl.c
    trunk/gcc/cp/tree.c
    trunk/gcc/dwarf2out.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree.c
    trunk/gcc/tree.h


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44188


  parent reply	other threads:[~2010-05-27 19:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  9:32 [Bug c++/44188] New: " rguenth at gcc dot gnu dot org
2010-05-18 21:50 ` [Bug c++/44188] " dodji at gcc dot gnu dot org
2010-05-20 11:07 ` dodji at gcc dot gnu dot org
2010-05-27 19:30 ` dodji at gcc dot gnu dot org [this message]
2010-05-27 19:36 ` dodji at gcc dot gnu dot org
2010-05-27 20:51 ` jakub at gcc dot gnu dot org
2010-05-28  0:03 ` dodji at gcc dot gnu dot org
2010-05-28  0:08 ` dodji at gcc dot gnu dot org
2010-06-05 20:03 ` dodji at gcc dot gnu dot org
2010-06-05 20:03 ` dodji at gcc dot gnu dot org
2010-06-06 18:25 ` dodji at gcc dot gnu dot org
2010-06-06 18:33 ` dodji at gcc dot gnu dot 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=20100527193017.10128.qmail@sourceware.org \
    --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).