From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Cary Coutant <ccoutant@google.com>,
Dodji Seketeli <dodji@redhat.com>,
GDB/Archer list <archer@sourceware.org>
Subject: Re: [RFC] Proposal for a new DWARF name index section
Date: Wed, 02 Dec 2009 19:39:00 -0000 [thread overview]
Message-ID: <20091202193852.GA23631@caradoc.them.org> (raw)
In-Reply-To: <m33a3tji36.fsf@fleche.redhat.com>
On Wed, Dec 02, 2009 at 12:23:25PM -0700, Tom Tromey wrote:
> I do think that slowing down the compiler to speed up the debugger would
> be the wrong tradeoff. I was hoping we could get this for free in the
> compiler, or nearly so, but now I unfortunately see that I was confused
> on that point :-(. We could pick a representation close to what gcc
> already emits -- but then that overly constrains gcc in the future.
That's not an option, anyway; the stuff GCC emits is too vague
in some cases (he says unsubstantiatedly).
> Caching is interesting but it comes with other problems. We have to
> manage the cache somehow. And, the cache would not be useful when an
> object changes. So, I'd prefer a direct approach, if one can be made to
> work.
Well, inherent in the cache approach (IMO) is a system-provided cache;
for installed libraries, the cache data could be added to a debuginfo
file. Of course, that assumes GDB's format stays "relatively stable"
across GDB updates.
> warm cache cold cache
> without canonicalization: ~0.5 sec 5 sec
> gdb does canonicalization: ~1.7 sec 6 sec
> gdb cvs head: ~2.4 sec 10 sec
Not bad!
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-12-02 19:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 9:04 Dodji Seketeli
2009-08-10 14:38 ` Jan Kratochvil
2009-08-10 17:36 ` Tom Tromey
2009-08-10 18:21 ` Jan Kratochvil
2009-08-11 7:55 ` Dodji Seketeli
2009-08-11 17:45 ` Jan Kratochvil
2009-08-11 22:43 ` Tom Tromey
2009-08-12 19:20 ` Jan Kratochvil
2009-08-11 22:29 ` Tom Tromey
2009-08-20 17:31 ` Dodji Seketeli
2009-11-17 23:46 ` Cary Coutant
2009-11-20 17:25 ` Tom Tromey
2009-11-22 4:39 ` Daniel Jacobowitz
2009-11-23 19:51 ` Tom Tromey
2009-12-01 19:14 ` Tom Tromey
2009-12-02 5:17 ` Daniel Jacobowitz
2009-12-02 17:07 ` Tom Tromey
2009-12-02 17:35 ` Daniel Jacobowitz
2009-12-02 19:23 ` Tom Tromey
2009-12-02 19:39 ` Daniel Jacobowitz [this message]
2009-12-03 1:46 ` Paul Pluzhnikov
2009-12-04 23:13 ` Tom Tromey
2009-12-06 3:41 ` Tom Tromey
2009-12-07 21:32 ` Tom Tromey
2009-12-02 16:11 ` Dodji Seketeli
2009-12-02 17:29 ` Tom Tromey
2009-12-11 23:56 ` Tom Tromey
2009-12-12 0:06 ` Daniel Jacobowitz
2009-12-12 0:13 ` Cary Coutant
2009-12-13 3:48 ` Dodji Seketeli
2009-12-14 15:32 ` Dodji Seketeli
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=20091202193852.GA23631@caradoc.them.org \
--to=drow@false.org \
--cc=archer@sourceware.org \
--cc=ccoutant@google.com \
--cc=dodji@redhat.com \
--cc=tromey@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).