public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nenad Vukicevic <nenad@intrepid.com>
To: gcc@gcc.gnu.org
Cc: jan.kratochvil@redhat.com, Gary Funck <gary@intrepid.com>
Subject: Re: dwarf2 - multiple DW_TAG_variable for global variable
Date: Sat, 09 Jan 2010 20:40:00 -0000	[thread overview]
Message-ID: <4B48E99B.6000508@intrepid.com> (raw)
In-Reply-To: <4B42EB7A.6000107@intrepid.com>

This dwarf code started appearing since this patch:

------------------------------------------------------------------------
r145293 | jakub | 2009-03-30 14:35:03 +0000 (Mon, 30 Mar 2009) | 11 lines

         PR debug/39563
         * c-decl.c (struct c_binding): Add locus field.
         (bind): Add locus argument, set locus field from it.
         (pop_scope): For b->nested VAR_DECL or FUNCTION_DECL,
         add a DECL_EXTERNAL copy of b->decl to current BLOCK_VARS.
         (push_file_scope, pushtag, pushdecl, pushdecl_top_level,
         implicitly_declare, undeclared_variable, lookup_label,
         declare_label, c_make_fname_decl, c_builtin_function,
         c_builtin_function_ext_scope, store_parm_decls_newstyle): Adjust
         bind callers.

Jan, can you confirm that this is indeed the correct DWARF that is being generated.

Thank you,
Nenad



On 1/4/10 11:34 PM, Nenad Vukicevic wrote:
> I installed gcc-4.5-20091224 snapshot and noticed that for simple 
> variable declaration
> I get two DW_TAG_variable dies in the object file. For example, the 
> following
> code
>
> int xxxxx;
> main()
> {xxxxx=1;}
>
> generates (with -g -gdwarf2 -O0 switches):
>
> <1><54>: Abbrev Number: 4 (DW_TAG_variable)
> <55>   DW_AT_name        : (indirect string, offset: 0x36): xxxxx
> <59>   DW_AT_decl_file   : 1
> <5a>   DW_AT_decl_line   : 1
> <5b>   DW_AT_type        : <0x4d>
> <5f>   DW_AT_external    : 1
> <60>   DW_AT_declaration : 1
> <1><61>: Abbrev Number: 5 (DW_TAG_variable)
> <62>   DW_AT_name        : (indirect string, offset: 0x36): xxxxx
> <66>   DW_AT_decl_file   : 1
> <67>   DW_AT_decl_line   : 1
> <68>   DW_AT_type        : <0x4d>
> <6c>   DW_AT_external    : 1
> <6d>   DW_AT_location    : 9 byte block: 3 0 0 0 0 0 0 0 0  
> (DW_OP_addr: 0)
>
> Is the above normal? 4.3.2 compiler generates only one die, the second 
> one with
> DW_AT_location attribute, which is correct.
>
> I also noticed that this example (were variable is not used):
>
> int xxxxx;
> main()
> {}
>
> generates only one DW_TAG_variable, the one  with DW_AT_location, 
> which again
> should be correct.
>
> I ran into this problem by porting some GDB code that uses DWARF2 and 
> got surprised
> to see this change from the previous version of gcc (4.3).
>
> Thanks,
> Nenad
>

  reply	other threads:[~2010-01-09 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05  7:34 Nenad Vukicevic
2010-01-09 20:40 ` Nenad Vukicevic [this message]
2010-01-09 21:02   ` Gary Funck
2010-01-09 21:18     ` Jan Kratochvil
2010-01-09 23:32       ` Nenad Vukicevic
2010-01-10  8:43         ` Jan Kratochvil

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=4B48E99B.6000508@intrepid.com \
    --to=nenad@intrepid.com \
    --cc=gary@intrepid.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jan.kratochvil@redhat.com \
    /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).