From: "Christian Biesinger (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Christian Biesinger <cbiesinger@google.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@sourceware.org>
Subject: [review v6] Store the mangled name as a string_view
Date: Tue, 22 Oct 2019 16:47:00 -0000 [thread overview]
Message-ID: <20191022164735.639552192E@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1571050562000.I24711ae2bcaa9e79ca89a6f8fda385d400419175@gnutoolchain-gerrit.osci.io>
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/37
......................................................................
Store the mangled name as a string_view
This should be a bit faster (because we can compare the size first),
but it is also a dependency for the next patch.
(3.47% of gdb startup time is spent in eq_demangled_name_entry when
attaching to Chrome's content_shell binary)
gdb/ChangeLog:
2019-10-22 Christian Biesinger <cbiesinger@google.com>
* symtab.c (struct demangled_name_entry): Change type of mangled
to gdb::string_view. Also adds a constructor that takes the
mangled name.
(hash_demangled_name_entry): Update.
(eq_demangled_name_entry): Update.
(free_demangled_name_entry): New function to call the destructor
now that this is not a POD anymore.
(create_demangled_names_hash): Pass free_demangled_name_entry to
htab_create_alloc.
(symbol_set_names): Update.
Change-Id: I24711ae2bcaa9e79ca89a6f8fda385d400419175
---
M gdb/ChangeLog
M gdb/symtab.c
2 files changed, 21 insertions(+), 7 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index a70f3e1..d271330 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,16 @@
+2019-10-22 Christian Biesinger <cbiesinger@google.com>
+
+ * symtab.c (struct demangled_name_entry): Change type of mangled
+ to gdb::string_view. Also adds a constructor that takes the
+ mangled name.
+ (hash_demangled_name_entry): Update.
+ (eq_demangled_name_entry): Update.
+ (free_demangled_name_entry): New function to call the destructor
+ now that this is not a POD anymore.
+ (create_demangled_names_hash): Pass free_demangled_name_entry to
+ htab_create_alloc.
+ (symbol_set_names): Update.
+
2019-10-21 Ali Tamur <tamu@google.com>
* dwarf2read.c (dir_index): Change type.
diff --git a/gdb/symtab.c b/gdb/symtab.c
index fc736fd..567d09d 100644
--- a/gdb/symtab.c
+++ b/gdb/symtab.c
@@ -68,6 +68,7 @@
#include "filename-seen-cache.h"
#include "arch-utils.h"
#include <algorithm>
+#include "gdbsupport/gdb_string_view.h"
#include "gdbsupport/pathstuff.h"
/* Forward declarations for local functions. */
@@ -713,7 +714,7 @@
/* Objects of this type are stored in the demangled name hash table. */
struct demangled_name_entry
{
- const char *mangled;
+ gdb::string_view mangled;
ENUM_BITFIELD(language) language : LANGUAGE_BITS;
char demangled[1];
};
@@ -726,7 +727,7 @@
const struct demangled_name_entry *e
= (const struct demangled_name_entry *) data;
- return htab_hash_string (e->mangled);
+ return iterative_hash (e->mangled.data (), e->mangled.length (), 0);
}
/* Equality function for the demangled name hash. */
@@ -739,7 +740,7 @@
const struct demangled_name_entry *db
= (const struct demangled_name_entry *) b;
- return strcmp (da->mangled, db->mangled) == 0;
+ return da->mangled == db->mangled;
}
/* Create the hash table used for demangled names. Each hash entry is
@@ -855,7 +856,7 @@
else
linkage_name_copy = linkage_name;
- entry.mangled = linkage_name_copy;
+ entry.mangled = gdb::string_view (linkage_name_copy, len);
slot = ((struct demangled_name_entry **)
htab_find_slot (per_bfd->demangled_names_hash.get (),
&entry, INSERT));
@@ -888,7 +889,7 @@
obstack_alloc (&per_bfd->storage_obstack,
offsetof (struct demangled_name_entry, demangled)
+ demangled_len + 1));
- (*slot)->mangled = linkage_name;
+ (*slot)->mangled = gdb::string_view (linkage_name, len);
}
else
{
@@ -904,7 +905,7 @@
+ len + demangled_len + 2));
mangled_ptr = &((*slot)->demangled[demangled_len + 1]);
strcpy (mangled_ptr, linkage_name_copy);
- (*slot)->mangled = mangled_ptr;
+ (*slot)->mangled = gdb::string_view (mangled_ptr, len);
}
(*slot)->language = gsymbol->language;
@@ -917,7 +918,7 @@
|| gsymbol->language == language_auto)
gsymbol->language = (*slot)->language;
- gsymbol->name = (*slot)->mangled;
+ gsymbol->name = (*slot)->mangled.data ();
if ((*slot)->demangled[0] != '\0')
symbol_set_demangled_name (gsymbol, (*slot)->demangled,
&per_bfd->storage_obstack);
next prev parent reply other threads:[~2019-10-22 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gerrit.1571050562000.I24711ae2bcaa9e79ca89a6f8fda385d400419175@gnutoolchain-gerrit.osci.io>
2019-10-16 13:08 ` [review] " Christian Biesinger (Code Review)
2019-10-21 20:15 ` [review v3] " Christian Biesinger (Code Review)
2019-10-21 22:39 ` Simon Marchi (Code Review)
2019-10-21 23:13 ` [review v5] " Christian Biesinger (Code Review)
2019-10-21 23:13 ` Christian Biesinger (Code Review)
2019-10-22 4:15 ` Simon Marchi (Code Review)
2019-10-22 16:06 ` Tom Tromey (Code Review)
2019-10-22 16:17 ` Christian Biesinger (Code Review)
2019-10-22 16:47 ` Christian Biesinger (Code Review) [this message]
2019-10-22 17:55 ` [pushed] " Sourceware to Gerrit sync (Code Review)
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=20191022164735.639552192E@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tromey@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