From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/dwarf] Support for attributes pointing to a different CU
Date: Mon, 04 Oct 2004 21:17:00 -0000 [thread overview]
Message-ID: <vt2hdpa2nkf.fsf@zenia.home> (raw)
In-Reply-To: <20041003161221.GA3234@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> writes:
> On Wed, Sep 29, 2004 at 12:49:35PM -0500, Jim Blandy wrote:
> > Since we never toss types anyway, would it make sense to move
> > type_hash to dwarf2_per_objfile?
>
> I don't think so. type_hash is used in two ways: individual items are
> set, when we know which CU we ought to have, and a whole CU is
> restored, when we know which CU we're restoring. It's always more
> efficient to have a lot of small hash tables if you know precisely
> which one you'll need; fewer collisions.
Really? libiberty/hashtab.c is a resizing hash table; I thought hash
table resizing was supposed to keep the collision rate roughly
constant (modulo hysteresis) regardless of the number of elements. If
that's not so, doesn't that mean your hash function isn't doing its
job spreading the elements across the (adequately sized) table?
next prev parent reply other threads:[~2004-10-04 21:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 4:57 Daniel Jacobowitz
2004-09-23 22:19 ` Jim Blandy
2004-09-23 22:33 ` Daniel Jacobowitz
2004-09-24 0:34 ` Daniel Jacobowitz
2004-09-28 22:43 ` Jim Blandy
2004-09-28 22:51 ` Jim Blandy
2004-09-28 22:57 ` Jim Blandy
2004-10-04 0:41 ` Daniel Jacobowitz
2004-10-04 22:12 ` Jim Blandy
2004-10-04 23:35 ` Daniel Jacobowitz
2004-10-05 5:13 ` Jim Blandy
2004-09-28 23:07 ` Jim Blandy
2004-10-03 16:28 ` Daniel Jacobowitz
2004-09-29 17:52 ` Jim Blandy
2004-10-03 16:12 ` Daniel Jacobowitz
2004-10-04 21:17 ` Jim Blandy [this message]
2004-10-04 21:22 ` Daniel Jacobowitz
2004-10-05 5:07 ` Jim Blandy
2004-10-05 13:48 ` Daniel Jacobowitz
2004-10-05 16:13 ` Jim Blandy
2004-10-05 16:11 ` Jim Blandy
2004-10-05 18:01 ` Daniel Jacobowitz
2004-10-05 19:24 ` Jim Blandy
2004-09-29 17:54 ` Jim Blandy
2004-09-29 19:53 ` Jim Blandy
2004-10-03 16:16 ` Daniel Jacobowitz
2004-09-29 20:19 ` Jim Blandy
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=vt2hdpa2nkf.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@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