Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: [Fwd: Re: c++/1512: no canonical way to output names of C++ types]
Date: Thu, 15 Jan 2004 16:25:00 -0000	[thread overview]
Message-ID: <20040115162531.GA2815@nevyn.them.org> (raw)
In-Reply-To: <4006BD4E.4050007@gnu.org>

On Thu, Jan 15, 2004 at 11:18:22AM -0500, Andrew Cagney wrote:
> > Fixes for this are in progress on drow-cplus-branch.  All the necessary
> > code is there, it just needs to be hooked up :)  I think I've gotten
> > derailed on some other problems first, though.  The basic problem is
> > that we want to canonicalize the names before adding them to the symbol
> > table, and that increases startup time.  I'm looking for ways to shave
> > startup time elsewhere.  I have a few ideas.
> 
> If it is going to be so expensive, can it be put off until later, when 
> the canonical value is needed?

Possibly.  We search for the canonical form in the symbol table, which
means we need to canonicalize before adding them to the (partial, full,
maybe minimal also) symbol table.  The trick will be delaying the
add-to-symbol-table until the symbol is needed, using a clever trick
suggested by Ian - keeping a list of pending symbols by basename,
basically.

There are some complications.  Particuarly, the code to infer classes'
fully qualified names depends on having the canonical demangled name
available.  I may be able to do something about this but I'm not sure
what yet.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-01-15 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 16:18 Andrew Cagney
2004-01-15 16:25 ` Daniel Jacobowitz [this message]
2004-01-15 16:33   ` Andrew Cagney
2004-01-15 16:47     ` Daniel Jacobowitz

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=20040115162531.GA2815@nevyn.them.org \
    --to=drow@mvista.com \
    --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