[switching mailing lists from binutils@ to gdb@]
> * "gdb used to take inordinate amount of time to load on our platform.
The
> fix was trivial, which likely means that few people ever use GDB on
> such large executables."
I believe one identified problem is how the symbol table uses hash
tables. The symbol tables are being given a careful upgrade. Was this
what you noticed?
No, it is handling BINCL records in STABS. I have replaced the linear search
in dbxread.c, function find_corresponding_bincl_psymtab() with hash table,
and this shaved 3 minutes off the GDB initialization time in our case
(on 333MHz Sparc Ultra).
Please note that our compiler is gcc 2.95, and that this is for STABS
debugging
format. I can send the diffs to the interested parties; they are for 5.0
GDB, though.