From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Keith Seitz <keiths@redhat.com>,
brobecker@adacore.com, psmith@gnu.org,
gdb-patches@sourceware.org
Subject: Re: [patch] Improve symbol lookup performance noted in PR 15519
Date: Fri, 31 May 2013 09:40:00 -0000 [thread overview]
Message-ID: <51A86FF5.9090401@redhat.com> (raw)
In-Reply-To: <20903.57436.871210.593441@ruffy.mtv.corp.google.com>
On 05/31/2013 12:27 AM, Doug Evans wrote:
> Hi.
> Here's the patch I intend to check in to "fix"
> http://sourceware.org/bugzilla/show_bug.cgi?id=15519
> [It's not a complete "fix", there's still some performance gains
> to be had, but I'm leaving that for a separate pass. This gets
> us >95% of the way there, at least in the benchmarks I've been using,
> including the one in the PR. Thanks Paul!]
>
> No regressions on amd64-linux, with/without Fission.
>
> I'll let it sit for a few days in case there are any more comments.
> I'd also like to commit this to the 7.6 branch. Ok Joel?
> [I need to rerun the testsuite in that tree before committing there.]
Thanks!
Absolutely no objections, but for my own education, and for the archives,
could you describe the gist of it? E.g., what is it that is slow, and what
is it that is being avoided to get the speedup? (where's the win?)
It isn't super obvious to me from reading the patch.
--
Pedro Alves
next prev parent reply other threads:[~2013-05-31 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 23:27 Doug Evans
2013-05-31 3:42 ` Joel Brobecker
2013-05-31 9:40 ` Pedro Alves [this message]
2013-05-31 22:33 ` Doug Evans
2013-06-03 6:01 ` Joel Brobecker
2013-06-03 17:27 ` Pedro Alves
2013-06-05 22:31 ` Doug Evans
2013-06-06 10:18 ` Pedro Alves
2013-06-06 19:03 ` Doug Evans
2013-06-07 14:50 ` Fix formating in copyright headers. (was: Re: [patch] Improve symbol lookup performance noted in PR 15519) Pedro Alves
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=51A86FF5.9090401@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=psmith@gnu.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