public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/48978] excessive hash table allocation for large lto build
Date: Fri, 13 May 2011 13:24:00 -0000	[thread overview]
Message-ID: <bug-48978-4-7HCoeZc0py@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48978-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48978

--- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-13 11:02:32 UTC ---
Author: rguenth
Date: Fri May 13 11:02:28 2011
New Revision: 173730

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173730
Log:
2011-05-13  Richard Guenther  <rguenther@suse.de>

    PR lto/48978
    * gimple.c (iterative_hash_gimple_type): Revert change in
    pointer target and function result and argument hashing.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/gimple.c


  parent reply	other threads:[~2011-05-13 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 15:25 [Bug lto/48978] New: " andi-gcc at firstfloor dot org
2011-05-12 15:35 ` Jan Hubicka
2011-05-12 16:04 ` [Bug lto/48978] " hubicka at ucw dot cz
2011-05-12 16:39 ` andi-gcc at firstfloor dot org
2011-05-12 16:55 ` andi-gcc at firstfloor dot org
2011-05-12 23:18 ` hubicka at ucw dot cz
2011-05-13 11:16 ` rguenth at gcc dot gnu.org
2011-05-13 13:24 ` rguenth at gcc dot gnu.org [this message]
2011-05-13 17:33 ` andi-gcc at firstfloor dot org
2011-06-06 11:06 ` andi-gcc at firstfloor dot org

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=bug-48978-4-7HCoeZc0py@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).