From: "Christian Biesinger (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: gdb-patches@sourceware.org
Cc: Christian Biesinger <cbiesinger@google.com>
Subject: [review] Don't make an extra copy + allocation of the demangled name
Date: Thu, 17 Oct 2019 22:47:00 -0000 [thread overview]
Message-ID: <gerrit.1571352433000.Ie6ad50e1e1e73509f55d756f0a437897bb93e3b0@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1571352433000.Ie6ad50e1e1e73509f55d756f0a437897bb93e3b0@gnutoolchain-gerrit.osci.io>
Christian Biesinger has uploaded a new change for review.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/132
......................................................................
Don't make an extra copy + allocation of the demangled name
We can just keep around the malloc()-ed name we got from bfd and free
it later.
gdb/ChangeLog:
2019-10-02 Christian Biesinger <cbiesinger@google.com>
* symtab.c (struct demangled_name_entry): Change demangled name
to a char*, now that we don't allocate it as part of the struct
anymore.
(free_demangled_name_entry): New function.
(create_demangled_names_hash): Pass free function to htab_create_alloc.
(symbol_set_names): No longer obstack allocate + copy the demangled
name, just store the allocated name from bfd.
Change-Id: Ie6ad50e1e1e73509f55d756f0a437897bb93e3b0
---
M gdb/symtab.c
1 file changed, 17 insertions(+), 18 deletions(-)
diff --git a/gdb/symtab.c b/gdb/symtab.c
index 8a551f1..a185f92 100644
--- a/gdb/symtab.c
+++ b/gdb/symtab.c
@@ -715,7 +715,7 @@
{
const char *mangled;
ENUM_BITFIELD(language) language : LANGUAGE_BITS;
- char demangled[1];
+ char* demangled;
};
/* Hash function for the demangled name hash. */
@@ -742,6 +742,15 @@
return strcmp (da->mangled, db->mangled) == 0;
}
+static void
+free_demangled_name_entry (void *data)
+{
+ struct demangled_name_entry *e
+ = (struct demangled_name_entry *) data;
+
+ xfree (e->demangled);
+}
+
/* Create the hash table used for demangled names. Each hash entry is
a pair of strings; one for the mangled name and one for the demangled
name. The entry is hashed via just the mangled name. */
@@ -756,7 +765,7 @@
per_bfd->demangled_names_hash.reset (htab_create_alloc
(256, hash_demangled_name_entry, eq_demangled_name_entry,
- NULL, xcalloc, xfree));
+ free_demangled_name_entry, xcalloc, xfree));
}
/* Try to determine the demangled name for a symbol, based on the
@@ -869,8 +878,6 @@
{
char *demangled_name_ptr
= symbol_find_demangled_name (gsymbol, linkage_name_copy);
- gdb::unique_xmalloc_ptr<char> demangled_name (demangled_name_ptr);
- int demangled_len = demangled_name ? strlen (demangled_name.get ()) : 0;
/* Suppose we have demangled_name==NULL, copy_name==0, and
linkage_name_copy==linkage_name. In this case, we already have the
@@ -886,39 +893,31 @@
*slot
= ((struct demangled_name_entry *)
obstack_alloc (&per_bfd->storage_obstack,
- offsetof (struct demangled_name_entry, demangled)
- + demangled_len + 1));
+ sizeof (demangled_name_entry)));
(*slot)->mangled = linkage_name;
}
else
{
- char *mangled_ptr;
-
/* If we must copy the mangled name, put it directly after
- the demangled name so we can have a single
+ the struct so we can have a single
allocation. */
*slot
= ((struct demangled_name_entry *)
obstack_alloc (&per_bfd->storage_obstack,
- offsetof (struct demangled_name_entry, demangled)
- + len + demangled_len + 2));
- mangled_ptr = &((*slot)->demangled[demangled_len + 1]);
+ sizeof (demangled_name_entry) + len + 1));
+ char *mangled_ptr = reinterpret_cast<char*> (*slot + 1);
strcpy (mangled_ptr, linkage_name_copy);
(*slot)->mangled = mangled_ptr;
}
+ (*slot)->demangled = demangled_name_ptr;
(*slot)->language = gsymbol->language;
-
- if (demangled_name != NULL)
- strcpy ((*slot)->demangled, demangled_name.get ());
- else
- (*slot)->demangled[0] = '\0';
}
else if (gsymbol->language == language_unknown
|| gsymbol->language == language_auto)
gsymbol->language = (*slot)->language;
gsymbol->name = (*slot)->mangled;
- if ((*slot)->demangled[0] != '\0')
+ if ((*slot)->demangled != nullptr)
symbol_set_demangled_name (gsymbol, (*slot)->demangled,
&per_bfd->storage_obstack);
else
next parent reply other threads:[~2019-10-17 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 22:47 Christian Biesinger (Code Review) [this message]
2019-10-21 23:19 ` Luis Machado (Code Review)
2019-10-22 4:32 ` Simon Marchi (Code Review)
2019-10-22 19:04 ` [review v2] " Christian Biesinger (Code Review)
2019-10-22 19:04 ` Christian Biesinger (Code Review)
2019-10-22 19:27 ` Simon Marchi (Code Review)
2019-10-23 16:51 ` [review v3] " Christian Biesinger (Code Review)
2019-10-25 18:23 ` Tom Tromey (Code Review)
2019-10-25 18:24 ` Tom Tromey (Code Review)
2019-10-25 19:10 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-10-25 19:10 ` [review v3] " Christian Biesinger (Code Review)
2019-10-25 19:10 ` [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=gerrit.1571352433000.Ie6ad50e1e1e73509f55d756f0a437897bb93e3b0@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.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