public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@bactrian.org>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: dwarves, hierarchies, and cross-references
Date: Sat, 10 May 2003 19:01:00 -0000	[thread overview]
Message-ID: <20030510190108.GA15014@nevyn.them.org> (raw)
In-Reply-To: <m3ptmryaph.fsf@papaya.bactrian.org>

On Fri, May 09, 2003 at 04:14:18PM -0700, David Carlton wrote:
> * Once we notice that we put E in the wrong context, update everybody
>   who has been misled by this.  This seems complicated and potentially
>   fragile to me: exactly what data would we have to maintain to make
>   this work?

Too fragile I think.

> * When parsing E via a cross-reference, figure out its context, so we
>   can name it correctly.  This seems like a plausible idea to me; I'm
>   only worried that it might be a little inefficient at times.

Yes.  We already read in the whole CU at a time and build the DIE
structure in memory, and then walk the DIE structure to build types. 
All we have to do is increase the memory usage of the DIEs slightly by
adding a backchain up the hierarchy.  A simliar thing works for
inter-CU references.  Then we can walk up the chain looking for
enclosing classes or namespaces, and get their names; and we have a
DIE->name convertor.

This requires some cleanup in the reader, but nothing revolutionary.

We also need the context in some other places.  For instance, to
associate method implementations to method declarations; and for
templates and inline functions.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-05-10 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 23:14 David Carlton
2003-05-10 19:01 ` Daniel Jacobowitz [this message]
2003-05-16 23:23   ` 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=20030510190108.GA15014@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@bactrian.org \
    --cc=gdb@sources.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).