public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29635] debug info of modules
Date: Mon, 18 Aug 2008 08:13:00 -0000 [thread overview]
Message-ID: <20080818081142.8030.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29635-10259@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from jakub at gcc dot gnu dot org 2008-08-18 08:11 -------
To expand on the duplicate DIE issue in C++, say:
namespace N
{
int i;
}
int foo ()
{
using N::i;
return i;
}
emits:
.uleb128 0x3 # (DIE (0x55) DW_TAG_imported_declaration)
.byte 0x1 # DW_AT_decl_file (mno2.C)
.byte 0x7 # DW_AT_decl_line
.long 0x6d # DW_AT_import
in foo (correct) and then:
.uleb128 0x5 # (DIE (0x64) DW_TAG_namespace)
.ascii "N\0" # DW_AT_name
.byte 0x1 # DW_AT_decl_file (mno2.C)
.byte 0x2 # DW_AT_decl_line
.long 0x8c # DW_AT_sibling
.uleb128 0x6 # (DIE (0x6d) DW_TAG_variable)
.ascii "i\0" # DW_AT_name
.byte 0x1 # DW_AT_decl_file (mno2.C)
.byte 0x3 # DW_AT_decl_line
.long .LASF0 # DW_AT_MIPS_linkage_name: "_ZN1N1iE"
.long 0x5d # DW_AT_type
.byte 0x1 # DW_AT_external
.byte 0x1 # DW_AT_declaration
.uleb128 0x6 # (DIE (0x7c) DW_TAG_variable)
.ascii "i\0" # DW_AT_name
.byte 0x1 # DW_AT_decl_file (mno2.C)
.byte 0x3 # DW_AT_decl_line
.long .LASF0 # DW_AT_MIPS_linkage_name: "_ZN1N1iE"
.long 0x5d # DW_AT_type
.byte 0x1 # DW_AT_external
.byte 0x1 # DW_AT_declaration
.byte 0x0 # end of children of DIE 0x64
.uleb128 0x7 # (DIE (0x8c) DW_TAG_variable)
.long 0x7c # DW_AT_specification
.byte 0x9 # DW_AT_location
.byte 0x3 # DW_OP_addr
.quad _ZN1N1iE
.byte 0x0 # end of children of DIE 0xb
Note not just 2, but 3, 2 DW_AT_declaration inside and one DW_AT_specification
DIE outside of the namespace. If extern int i; is used instead, then the
DW_AT_specification is missing.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu dot
| |org, drow at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29635
next prev parent reply other threads:[~2008-08-18 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 14:02 [Bug fortran/29635] New: " fxcoudert at gcc dot gnu dot org
2006-10-29 14:04 ` [Bug fortran/29635] " steven at gcc dot gnu dot org
2007-01-02 14:35 ` fxcoudert at gcc dot gnu dot org
2007-01-02 15:27 ` stevenb dot gcc at gmail dot com
2007-08-11 22:09 ` dfranke at gcc dot gnu dot org
2007-08-12 10:36 ` stevenb dot gcc at gmail dot com
2008-08-15 18:30 ` jakub at gcc dot gnu dot org
2008-08-15 20:20 ` jakub at gcc dot gnu dot org
2008-08-18 8:13 ` jakub at gcc dot gnu dot org [this message]
2008-08-18 8:44 ` jakub at gcc dot gnu dot org
2008-08-18 12:40 ` drow at gcc dot gnu dot org
2008-08-29 18:43 ` jakub at gcc dot gnu dot org
2009-04-10 21:39 ` dfranke at gcc dot gnu dot org
2009-05-29 7:45 ` burnus at gcc dot gnu dot org
2009-05-29 8:52 ` 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=20080818081142.8030.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).