public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: Richard Guenther <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][4.4] Add a global DECL_UID -> tree mapping
Date: Sat, 23 Feb 2008 00:31:00 -0000	[thread overview]
Message-ID: <47BF5EEB.2030107@google.com> (raw)
In-Reply-To: <47BF1BCF.8010300@redhat.com>

On 2/22/08 2:00 PM, Andrew MacLeod wrote:

> This oughta fix the odd compile time hit we have when the hash table 
> doesn't perform well too eh? I remember looking at something a few weeks 
> ago where most of the operand scan time (which was needlessly excessive) 
> was almost all in referenced_var hash table lookups.  getting rid of 
> that hash lookup is a good thing.

Indeed.  I like this change quite a bit.  Thanks for working on this 
Richard.


Diego.

  reply	other threads:[~2008-02-23  0:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 15:03 Richard Guenther
2008-02-22 13:51 ` Richard Guenther
2008-02-22 19:16   ` Andrew MacLeod
2008-02-23  0:31     ` Diego Novillo [this message]
2008-02-23 12:51       ` Richard Guenther
2008-02-25 16:10       ` Richard Guenther

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=47BF5EEB.2030107@google.com \
    --to=dnovillo@google.com \
    --cc=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).