From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb <gdb@sources.redhat.com>, Elena Zannoni <ezannoni@redhat.com>,
Jim Blandy <jimb@redhat.com>
Subject: Re: DW_AT_specification and partial symtabs
Date: Thu, 12 Jun 2003 17:10:00 -0000 [thread overview]
Message-ID: <ro1brx36x2z.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030612170545.GA16995@nevyn.them.org>
On Thu, 12 Jun 2003 13:05:45 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> I'll answer this in more depth in a bit. For now, something to
> consider: I would like to add .debug_typenames (spelling?) to GCC -
> it's an SGI extension, IIRC.
Yes. It's actually .debug_pubtypes, and has made it into the DWARF 3
spec. (Though the description there could use some work.)
I don't think that I'm too likely to do that myself, though, for
various reasons.
>> void foo ()
>> {
>> class Local {
>> public:
>> int mem() {return 1;}
>> };
>>
>> ...
>> }
>>
>> then is the compiler allowed to put a definition of Local::mem as a
>> child of the comp unit die (with a DW_AT_specification pointing to a
>> DIE inside of foo somewhere)?
> I believe so.
Ulgh. That's what I think, too.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-06-12 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 17:01 David Carlton
2003-06-12 17:05 ` Daniel Jacobowitz
2003-06-12 17:10 ` David Carlton [this message]
2003-06-12 17:20 ` Elena Zannoni
2003-06-12 22:17 ` David Carlton
2003-06-13 13:36 ` Daniel Jacobowitz
2003-06-13 14:00 ` Elena Zannoni
2003-06-13 15:38 ` Andrew Cagney
2003-06-13 15:50 ` Daniel Jacobowitz
2003-06-13 15:57 ` Andrew Cagney
2003-06-13 16:24 ` Andrew Cagney
2003-06-13 16:34 ` Daniel Jacobowitz
2003-06-17 0:09 ` David Carlton
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=ro1brx36x2z.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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