public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dfranke 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: Sat, 11 Aug 2007 22:09:00 -0000 [thread overview] Message-ID: <20070811220814.26530.qmail@sourceware.org> (raw) In-Reply-To: <bug-29635-10259@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from dfranke at gcc dot gnu dot org 2007-08-11 22:08 ------- gfortran seems to lack the following information: 1. DW_TAG_module to describe the module at hand 2. DW_TAG_imported_declaration/DW_TAG_imported_module/DW_AT_import to describe use-associated variables (dwarf2, sec. 4.3; dwarf3, sec. 3.2.3 and 3.2.4) The former is generated by ifort, the latter is not. As dwarf3, sec 3.2, indicates similarities of modules to C++ namespaces, it could be worth a try to see how it is implemented over there. The equivalent C++-code: $> cat a.cpp #include <cstdio> namespace foo { int i = 42; } int main() { using namespace foo; printf("%d\n", i); return 0; } $> g++ -g a.cpp $> readelf [...] <1><ad3>: Abbrev Number: 29 (DW_TAG_subprogram) DW_AT_external : 1 DW_AT_name : main DW_AT_decl_file : 1 DW_AT_decl_line : 17 DW_AT_type : <109> DW_AT_low_pc : 0x8048484 DW_AT_high_pc : 0x80484b8 DW_AT_frame_base : 0 (location list) DW_AT_sibling : <af8> <2><af0>: Abbrev Number: 30 (DW_TAG_imported_module) DW_AT_decl_file : 1 DW_AT_decl_line : 18 DW_AT_import : <af8> <1><af8>: Abbrev Number: 4 (DW_TAG_namespace) DW_AT_name : foo DW_AT_decl_file : 1 DW_AT_decl_line : 13 DW_AT_sibling : <b1a> <2><b03>: Abbrev Number: 31 (DW_TAG_variable) DW_AT_name : i DW_AT_decl_file : 1 DW_AT_decl_line : 14 DW_AT_MIPS_linkage_name: _ZN3foo1iE DW_AT_type : <109> DW_AT_external : 1 DW_AT_declaration : 1 <1><b1a>: Abbrev Number: 32 (DW_TAG_variable) DW_AT_specification: <b03> DW_AT_location : 5 byte block: 3 ec 96 4 8 (DW_OP_addr: 80496ec) [...] Steven, are you (still) working on this? -- dfranke at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfranke at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29635
next prev parent reply other threads:[~2007-08-11 22:09 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 [this message] 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 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=20070811220814.26530.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).