public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [RFA 0/2] some minor symbol-reading performance improvements
Date: Sat, 04 Nov 2017 16:14:00 -0000	[thread overview]
Message-ID: <20171104161356.17565-1-tom@tromey.com> (raw)

This week I looked into symbol-reading performance a little bit.
Using callgrind, I found a couple of simple ways to improve
performance.

This series was regression tested by the buildbot.

Tom

             reply	other threads:[~2017-11-04 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 16:14 Tom Tromey [this message]
2017-11-04 16:14 ` [RFA 2/2] Simplify the psymbol hash function Tom Tromey
2017-11-08 11:12   ` Pedro Alves
2017-11-08 11:42     ` Pedro Alves
2017-11-08 19:08       ` Tom Tromey
2017-11-09 14:09         ` Tom Tromey
2017-11-09 14:10           ` Pedro Alves
2017-11-04 16:14 ` [RFA 1/2] Speed up dict_hash Tom Tromey
2017-11-08 10:46   ` Pedro Alves
2017-11-08 18:44     ` Tom Tromey
2017-11-08 22:41       ` Pedro Alves
2017-11-08 23:01         ` Tom Tromey
2017-11-08 23:51           ` 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=20171104161356.17565-1-tom@tromey.com \
    --to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).