public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/45997] New: __unknown__ type name for typedef'd int Date: Wed, 13 Oct 2010 04:48:00 -0000 [thread overview] Message-ID: <bug-45997-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45997 Summary: __unknown__ type name for typedef'd int Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: dje@google.com Earlier versions of gcc (e.g. 4.4.3) would emit a DW_TAG_base_type without a name. svn head emits one with name "__unknown__". typedef int my_int; typedef const my_int const_my_int; typedef volatile const_my_int volatile_const_my_int; my_int v_my_int (0); const_my_int v_const_my_int (1); volatile_const_my_int v_volatile_const_my_int (4); int main () { return 0; } g++ -g -S -dA foo.cc -o - | grep __unknown__ --> .long .LASF3 # DW_AT_name: "__unknown__" .string "__unknown__"
next reply other threads:[~2010-10-13 4:48 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-13 4:48 dje at google dot com [this message] 2010-10-27 23:00 ` [Bug debug/45997] [4.6 Regression] " pinskia at gcc dot gnu.org 2010-11-03 13:21 ` jakub at gcc dot gnu.org 2010-11-03 14:08 ` jakub at gcc dot gnu.org 2010-11-08 22:39 ` dodji at gcc dot gnu.org 2010-11-12 11:59 ` dodji at gcc dot gnu.org 2010-11-12 12:05 ` dodji at gcc dot gnu.org 2010-12-06 19:34 ` jakub at gcc dot gnu.org 2010-12-06 19:41 ` 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-45997-4@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).