From: Doug Evans <dje@google.com>
To: gdb-patches <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFC] symbol lookup cache
Date: Wed, 03 Dec 2014 00:50:00 -0000 [thread overview]
Message-ID: <CADPb22SwQGcJPQFsPy0w1EOurknejRDa1pPHB8KxRarbu1jY8g@mail.gmail.com> (raw)
In-Reply-To: <yjt2y4qrlqwa.fsf@ruffy.mtv.corp.google.com>
On Mon, Dec 1, 2014 at 12:23 AM, Doug Evans <dje@google.com> wrote:
>
> Hi.
>
> Holidays are nice for having the time to take on
> projects one is interested in but doesn't have
> time to otherwise do.
>
> I looked at a couple of areas for improvement
> in gdb's symbol handling over the last couple
> of days. One is .gdb_index support for tab
> completion, which is the topic for another mail.
> This email is about a symbol lookup cache.
>
> ..gdb_index helps speed things up for one objfile,
> but when there are 100s (or 1000s) of shared
> libraries, symbol lookup can still take awhile,
> even with .gdb_index.
> [I'm setting aside a planned change to basic
> symbol lookup to use the index better.
> We'll still, I think, want a cache even
> with that change.]
>
> This patch still needs more testing
> and I need to collect more perf data,
> but it's a start at caching symbol lookups.
> This first pass is just for the case
> where we iterate over all objfiles for
> lookups in the global or static blocks.
> Low hanging fruit.
> At the moment it's just RFC.
[bleah, sorry for the repeat Joel]
One thing this patch is missing is the ability to turn the cache off,
both for performance measurements and for debugging.
next prev parent reply other threads:[~2014-12-03 0:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 8:23 Doug Evans
2014-12-03 0:50 ` Doug Evans [this message]
2014-12-20 7:57 ` [PATCH] " Doug Evans
2014-12-20 8:29 ` Doug Evans
2014-12-20 10:43 ` Eli Zaretskii
2014-12-20 19:14 ` Doug Evans
2014-12-20 19:55 ` Eli Zaretskii
2014-12-20 21:04 ` Doug Evans
2014-12-21 3:34 ` Eli Zaretskii
2014-12-21 18:51 ` Doug Evans
2014-12-21 21:01 ` Joel Brobecker
2014-12-22 2:04 ` Doug Evans
2014-12-22 12:48 ` Joel Brobecker
2015-01-11 19:11 ` Doug Evans
2014-12-03 2:46 ` [RFC] " Joel Brobecker
2014-12-04 16:38 ` Pedro Alves
2014-12-04 19:17 ` Doug Evans
2014-12-04 19:16 ` Jan Kratochvil
2014-12-04 19:24 ` Doug Evans
2014-12-04 19:28 ` Jan Kratochvil
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=CADPb22SwQGcJPQFsPy0w1EOurknejRDa1pPHB8KxRarbu1jY8g@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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