public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/45048] duplicate DW_TAG_variable Date: Fri, 23 Jul 2010 21:06:00 -0000 [thread overview] Message-ID: <20100723210609.13536.qmail@sourceware.org> (raw) In-Reply-To: <bug-45048-360@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from tromey at gcc dot gnu dot org 2010-07-23 21:06 ------- I suppose the duplicate is due to the "i" inside of "f". But inside of f I see: <2><78>: Abbrev Number: 7 (DW_TAG_lexical_block) <79> DW_AT_low_pc : 0x3 <7d> DW_AT_high_pc : 0x8 <3><81>: Abbrev Number: 4 (DW_TAG_variable) <82> DW_AT_name : i <84> DW_AT_decl_file : 1 <85> DW_AT_decl_line : 6 <86> DW_AT_MIPS_linkage_name: (indirect string, offset: 0xb): _ZN1S1iE <8a> DW_AT_type : <0x5c> <8e> DW_AT_external : 1 <8f> DW_AT_declaration : 1 I think this would be clearer if "i" were declared using DW_AT_import, or at the very least using the outer declaration as a specification. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45048
next prev parent reply other threads:[~2010-07-23 21:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-23 17:54 [Bug debug/45048] New: " tromey at gcc dot gnu dot org 2010-07-23 21:06 ` tromey at gcc dot gnu dot org [this message] 2010-07-27 10:40 ` [Bug debug/45048] " jakub at gcc dot gnu dot org 2010-07-27 11:14 ` jakub 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=20100723210609.13536.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: 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).