From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Symbol table hashing patch
Date: Mon, 01 Oct 2001 16:38:00 -0000 [thread overview]
Message-ID: <20011001193830.A11559@nevyn.them.org> (raw)
In-Reply-To: <15288.63593.410425.572868@krustylu.cygnus.com>
On Mon, Oct 01, 2001 at 07:12:41PM -0400, Elena Zannoni wrote:
>
>
> As a first comment,, I would strongly reccommend that you break the
> ALL_BLOCK_SYMBOLS changes into a separate patch. That way the
> significant changes to the symtab algorithms will become easier to
> review. It seems from you comments that the MINIMAL_SYMBOL_HASH_SIZE
> is also an independent fix. How about the bug in msymtab_hash_iw, can
> that be separated out as well?
>
> What is 113?
>
Yes, msymtab_hash_iw is also independent.
I'll start breaking it up. On the other hand, I can't do all of it until I
get a little feedback - particularly, the sorting issues. So I would
appreciate any comments on the questions asked in the original message.
As for 113, the exact value is up for debate, but it shows a bit of a
problem with the current hash functions: the values of *string are not
evenly distributed. Multiplying by 31 and then adding an ASCII value
of (usually) ~100 doesn't seem very effective. The thing to do would
probably be to take advantage of Zack Weinberg's recent research; he
spent some time finding a good hash function for the set of
identifiers GCC deals with. It's the same one that this patch
introduces:
#define HASHSTEP(r, c) ((r) * 67 + ((c) - 113));
For reference, the post is:
http://gcc.gnu.org/ml/gcc-patches/2001-08/msg01021.html
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-10-01 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 15:46 Daniel Jacobowitz
2001-10-01 16:05 ` Elena Zannoni
2001-10-01 16:38 ` Daniel Jacobowitz [this message]
2001-10-01 17:40 ` Daniel Berlin
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=20011001193830.A11559@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@cygnus.com \
--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