From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 2/4] dwarf2_physname
Date: Thu, 04 Feb 2010 17:21:00 -0000 [thread overview]
Message-ID: <m3y6j8kjbr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100201164837.GF21339@caradoc.them.org> (Daniel Jacobowitz's message of "Mon, 1 Feb 2010 11:48:37 -0500")
>>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:
>> +die_needs_namespace (struct die_info *die, struct dwarf2_cu *cu)
>> {
[...]
>> + case DW_TAG_variable:
>> + {
>> + struct attribute *attr;
>> + attr = dwarf2_attr (die, DW_AT_specification, cu);
>> + if (attr)
>> + return 1;
>> + attr = dwarf2_attr (die, DW_AT_external, cu);
>> + if (attr == NULL && die->parent->tag != DW_TAG_namespace)
>> + return 0;
>> + return 1;
Daniel> What's this about? It needs an explanation, and I don't think
Daniel> DW_AT_specification has anything to do with die_needs_namespace.
I read through this sub-thread a little, and looked at the DWARF spec
too.
Here is what I believe to be the relevant text from the spec:
If a type, variable, or function declared in a namespace is defined
outside of the body of the namespace declaration, that type, variable,
or function definition entry has a DW_AT_specification attribute whose
value is a reference to the debugging information entry representing the
declaration of the type, variable or function. Type, variable, or
function entries with a DW_AT_specification attribute do not need to
duplicate information provided by the declaration entry referenced by
the specification attribute.
So, if a DIE has a DW_AT_specification, then we must use the namespace
indicated by the referenced DIE. If it does not have DW_AT_specification,
then we use its own parentage.
It is not clear to me whether it is possible for a DIE to have a
DW_AT_specification referring to another DIE which is not in a
namespace. Offhand this seems invalid, but if it does occur, it could
be supported in this function with just a little more effort.
I don't understand why die_needs_namespace only does this for
DW_TAG_variable and not other things. I also don't understand why it
unconditionally returns 1 for enumerators, functions, and the like.
However, I didn't look to see how it is used, so perhaps it doesn't
matter.
After reading more of the thread, maybe I am missing the point.
Tom
next prev parent reply other threads:[~2010-02-04 17:21 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 21:20 Keith Seitz
2009-11-20 22:10 ` Daniel Jacobowitz
2009-11-21 0:04 ` Tom Tromey
2009-11-21 3:46 ` Frank Ch. Eigler
2009-11-23 18:06 ` Tom Tromey
2009-11-23 19:00 ` Daniel Jacobowitz
2009-11-23 16:52 ` Keith Seitz
2009-11-23 17:08 ` Daniel Jacobowitz
2009-11-24 19:20 ` Sami Wagiaalla
2010-01-27 17:10 ` Sami Wagiaalla
2009-12-08 19:47 ` Keith Seitz
2009-12-14 19:33 ` Keith Seitz
2009-12-17 20:19 ` Tom Tromey
2009-12-17 20:28 ` Daniel Jacobowitz
2009-12-17 22:39 ` Paul Pluzhnikov
2009-12-22 18:35 ` Tom Tromey
2009-12-22 19:24 ` Daniel Jacobowitz
2010-01-20 20:37 ` Keith Seitz
2010-01-26 21:17 ` Daniel Jacobowitz
2010-01-27 19:12 ` Keith Seitz
2010-01-28 20:22 ` Keith Seitz
2010-01-28 20:24 ` Daniel Jacobowitz
2010-01-28 23:41 ` Keith Seitz
2010-02-01 16:48 ` Daniel Jacobowitz
2010-02-01 19:32 ` Keith Seitz
2010-02-01 19:39 ` Daniel Jacobowitz
2010-02-01 21:52 ` Keith Seitz
2010-02-01 22:19 ` Daniel Jacobowitz
2010-02-02 23:23 ` Keith Seitz
2010-02-02 23:31 ` Keith Seitz
2010-02-03 2:46 ` Daniel Jacobowitz
2010-02-04 17:48 ` Tom Tromey
2010-02-04 18:14 ` Daniel Jacobowitz
2010-02-05 17:13 ` Keith Seitz
2010-02-05 17:29 ` Daniel Jacobowitz
2010-02-05 20:24 ` Keith Seitz
2010-02-05 20:57 ` Daniel Jacobowitz
2010-02-05 23:10 ` Keith Seitz
2010-02-05 23:46 ` Daniel Jacobowitz
2010-02-04 17:21 ` Tom Tromey [this message]
2010-02-04 17:25 ` Daniel Jacobowitz
2009-11-23 7:31 ` André Pönitz
2009-11-23 16:57 ` Keith Seitz
2009-11-23 17:20 ` Tom Tromey
2009-11-24 7:22 ` André Pönitz
2009-11-24 22:54 ` Tom Tromey
2009-11-25 9:16 ` André Pönitz
2009-11-25 18:14 ` Tom Tromey
2009-11-23 17:15 ` Tom Tromey
2009-11-24 22:11 ` Joel Brobecker
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=m3y6j8kjbr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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