public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Add new overload of dwarf5_djb_hash Date: Tue, 12 Apr 2022 15:39:50 +0000 (GMT) [thread overview] Message-ID: <20220412153950.D38513858C27@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4e9e4fcda5e820d770369824669d86d3fadcad04 commit 4e9e4fcda5e820d770369824669d86d3fadcad04 Author: Tom Tromey <tom@tromey.com> Date: Sun Mar 21 11:15:57 2021 -0600 Add new overload of dwarf5_djb_hash This adds a new overload of dwarf5_djb_hash. This is used in subsequent patches. Diff: --- gdb/dwarf2/index-common.c | 14 ++++++++++++++ gdb/dwarf2/index-common.h | 4 ++++ 2 files changed, 18 insertions(+) diff --git a/gdb/dwarf2/index-common.c b/gdb/dwarf2/index-common.c index c2bb1c6f78e..d8f9973d6cc 100644 --- a/gdb/dwarf2/index-common.c +++ b/gdb/dwarf2/index-common.c @@ -54,3 +54,17 @@ dwarf5_djb_hash (const char *str_) hash = hash * 33 + tolower (c); return hash; } + +/* See dwarf-index-common.h. */ + +uint32_t +dwarf5_djb_hash (gdb::string_view str) +{ + /* Note: tolower here ignores UTF-8, which isn't fully compliant. + See http://dwarfstd.org/ShowIssue.php?issue=161027.1. */ + + uint32_t hash = 5381; + for (char c : str) + hash = hash * 33 + tolower (c & 0xff); + return hash; +} diff --git a/gdb/dwarf2/index-common.h b/gdb/dwarf2/index-common.h index 049e1d894f1..cbfb88a4e98 100644 --- a/gdb/dwarf2/index-common.h +++ b/gdb/dwarf2/index-common.h @@ -52,4 +52,8 @@ hashval_t mapped_index_string_hash (int index_version, const void *p); uint32_t dwarf5_djb_hash (const char *str_); +/* Symbol name hashing function as specified by DWARF-5. */ + +uint32_t dwarf5_djb_hash (gdb::string_view str_); + #endif /* DWARF_INDEX_COMMON_H */
reply other threads:[~2022-04-12 15:39 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220412153950.D38513858C27@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).