This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/16994] performance issue looking up static symbols (e.g. int, int64 typedef).
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 29 May 2014 23:32:19 +0000
- Subject: [Bug symtab/16994] performance issue looking up static symbols (e.g. int, int64 typedef).
- Auto-submitted: auto-generated
- References: <bug-16994-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16994
--- Comment #1 from dje at google dot com ---
In the .gdb_index of the monster benchmark I'm using, there are 10K entries for
int64, and none for void.
Thus any time gdb iterates over symbol tables to look up void, it's a total
waste of time.
gdb should probably (still TBD) use .gdb_index for STATIC_BLOCK lookups in
addition to GLOBAL_BLOCK lookups (see pr 16998), before iterating over all
currently expanded symtabs. But I think the case of looking up "void" is a
good example of needing to look in the default set (provided by the arch) after
looking in the current CU for STATIC_BLOCK lookups.
--
You are receiving this mail because:
You are on the CC list for the bug.