From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Christian Biesinger <cbiesinger@google.com>
Subject: [PATCH v2 0/3] Speed up hashing in demangled_names_hash
Date: Tue, 08 Oct 2019 16:09:00 -0000 [thread overview]
Message-ID: <20191008160933.155975-1-cbiesinger@google.com> (raw)
Use a faster hash function (via an optional dependency) and makes
equality comparison slightly faster (by comparing the length first).
Changes from v1:
- Rebased
- fast_hash now does not require nulltermination
- Updated commit message & benchmark data for patch 3/3
Christian Biesinger (3):
Store the mangled name as a string_view
Add a fast_hash function in common-utils
Use libxxhash for hashing, if present
gdb/Makefile.in | 8 +-
gdb/config.in | 3 +
gdb/configure | 493 +++++++++++++++++++++++++++++++++++++++++++++++
gdb/configure.ac | 19 ++
gdb/symtab.c | 16 +-
gdb/utils.c | 14 ++
gdb/utils.h | 2 +
7 files changed, 546 insertions(+), 9 deletions(-)
--
2.23.0.581.g78d2f28ef7-goog
next reply other threads:[~2019-10-08 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 16:09 Christian Biesinger via gdb-patches [this message]
2019-10-08 16:09 ` [PATCH v2 1/3] Store the mangled name as a string_view Christian Biesinger via gdb-patches
2019-10-08 16:09 ` [PATCH v2 2/3] Add a fast_hash function in common-utils Christian Biesinger via gdb-patches
2019-10-08 16:09 ` [PATCH v2 3/3] Use libxxhash for hashing, if present Christian Biesinger via gdb-patches
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=20191008160933.155975-1-cbiesinger@google.com \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.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).