public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matt Austern <austern@apple.com>
To: Jakub Jelinek <jakub@redhat.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 18:14:00 -0000	[thread overview]
Message-ID: <753A527A-1F9E-11D9-8C49-000A95BCF344@apple.com> (raw)
In-Reply-To: <20041016094708.GZ31909@devserv.devel.redhat.com>

On Oct 16, 2004, at 2:47 AM, Jakub Jelinek wrote:

> The hash table contains 21249 NULLs, then full slots (with a couple
> of NULLs near the beginning, but only a few), and from slot 37875
> onwards till the end of the hash table there are NULLs again.
>
> Shouldn't we multiply by 2^64 / phi instead of 2^32 / phi when
> long is 64-bit?

Oops, you're right.  Sorry; I didn't test on a 64-bit platform.

			--Matt

  parent reply	other threads:[~2004-10-16 18:09 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
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 [this message]
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=753A527A-1F9E-11D9-8C49-000A95BCF344@apple.com \
    --to=austern@apple.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).