From: Jakub Jelinek <jakub@redhat.com>
To: Matt Austern <austern@apple.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Committed] Use special-purpose hash table to speed up walk_tree
Date: Sat, 16 Oct 2004 11:49:00 -0000 [thread overview]
Message-ID: <20041016112017.GB31909@devserv.devel.redhat.com> (raw)
In-Reply-To: <20041016103712.GA31909@devserv.devel.redhat.com>
On Sat, Oct 16, 2004 at 06:37:12AM -0400, Jakub Jelinek wrote:
> On Sat, Oct 16, 2004 at 05:47:08AM -0400, Jakub Jelinek wrote:
> > But on x86-64-redhat-linux essentially makes even bootstrap impossible
> > (well, I have killed it after it spent more than 10 minutes compiling
> > insn-recog or insn-attrtab by stage1/cc1).
> > hash1's distribution is less than perfect.
>
> For the hash function I'm trying these patches now:
>
> (both do the same, not sure if the first one is ok regarding absolute
> portability).
With either of these patches the average chain length on the same
table (16384 pointers, 65536 slots) is 1.1, there is one occurence of 4 pointers
hashed into the same slot and 44 times 3 pointers hashed into the same
slot, but never more.
Ok to commit? Is the #if ULONG_MAX > UINT_MAX ok, or should I commit the
one without #ifs?
Jakub
next prev parent reply other threads:[~2004-10-16 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 23:22 Matt Austern
2004-10-14 23:24 ` Phil Edwards
2004-10-15 0:04 ` Matt Austern
2004-10-16 10:17 ` Jakub Jelinek
2004-10-16 10:37 ` Steven Bosscher
2004-10-17 8:30 ` Mark Mitchell
2004-10-17 10:59 ` Steven Bosscher
2004-10-17 18:45 ` Matt Austern
2004-10-18 4:19 ` Mark Mitchell
2004-10-21 21:25 ` Gerald Pfeifer
2004-10-16 10:42 ` Jakub Jelinek
2004-10-16 11:49 ` Jakub Jelinek [this message]
2004-10-16 18:29 ` Matt Austern
2004-10-16 18:35 ` Richard Henderson
2004-10-16 18:37 ` Jakub Jelinek
2004-10-16 18:51 ` Richard Henderson
2004-10-16 19:15 ` Jakub Jelinek
2004-10-17 1:11 ` Richard Henderson
2004-10-16 18:14 ` Matt Austern
2004-10-18 14:48 Richard Kenner
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=20041016112017.GB31909@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=austern@apple.com \
--cc=gcc-patches@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).