From: Jakub Jelinek <jakub@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: A gdb+bfd string pool?
Date: Fri, 31 Oct 2003 17:36:00 -0000 [thread overview]
Message-ID: <20031031153157.GZ12344@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <3FA29BDF.1000100@redhat.com>
On Fri, Oct 31, 2003 at 12:29:03PM -0500, Andrew Cagney wrote:
>
> >>The interface or the implementation? The bcache interface is focused
> >>and simple (something that can't be said for that hash table). The
> >>hashtab could certainly be used in the implementation (as elf-strtab did).
> >
> >
> >So does gdb/symtab.c.
> >
> >
> >>Anyway, back to the question. Does a [global] common pool make sense
> >>for BFD?
> >
> >
> >Oh, you meant an _instance_, not a data structure. Sorry.
>
> More specifically, a single instance. Instead of having something like
> a per-object file symbol bcache as was done with GDB, there would just
> be a single global bcache (and it would never shrink).
elf-strtab has a property which I'm not sure you really need in GDB,
as it slow things down. It attempts to do suffix merging, ie. if you have
p = "abcde" and q = "cde", r = "cde", s = "abcde" strings,
then p = "abcde", q = p + 2, r = q, s = p. Storing strings in a hashtable
is certainly cheaper for CPU time than this.
Jakub
next prev parent reply other threads:[~2003-10-31 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 15:15 Andrew Cagney
2003-10-31 15:19 ` Daniel Jacobowitz
2003-10-31 15:45 ` Andrew Cagney
2003-10-31 15:51 ` Daniel Jacobowitz
2003-10-31 17:29 ` Andrew Cagney
2003-10-31 17:36 ` Jakub Jelinek [this message]
2003-10-31 17:45 ` Andrew Cagney
2003-11-03 17:25 ` David Carlton
2003-11-04 8:16 ` Joel Brobecker
2003-11-04 16:31 ` Andrew Cagney
2003-11-04 23:51 ` Andrew Cagney
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=20031031153157.GZ12344@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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