From: "H.J. Lu" <hjl.tools@gmail.com>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][?/n] Cleanup LTO type merging
Date: Tue, 17 May 2011 15:32:00 -0000 [thread overview]
Message-ID: <BANLkTinsamHOGi6VsgjsJTQTGtsQ0EMoig@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1105171229400.810@zhemvz.fhfr.qr>
On Tue, May 17, 2011 at 3:29 AM, Richard Guenther <rguenther@suse.de> wrote:
> On Mon, 16 May 2011, H.J. Lu wrote:
>
>> On Mon, May 16, 2011 at 7:17 AM, Richard Guenther <rguenther@suse.de> wrote:
>> >
>> > The following patch improves hashing types by re-instantiating the
>> > patch that makes us visit aggregate target types of pointers and
>> > function return and argument types. This halves the collision
>> > rate on the type hash table for a linux-kernel build and improves
>> > WPA compile-time from 3mins to 1mins and reduces memory usage by
>> > 1GB for that testcase.
>> >
>> > Bootstrapped and tested on x86_64-unknown-linux-gnu, SPEC2k6
>> > build-tested.
>> >
>> > Richard.
>> >
>> > (patch is reversed)
>> >
>> > 2011-05-16 Richard Guenther <rguenther@suse.de>
>> >
>> > * gimple.c (iterative_hash_gimple_type): Re-instantiate
>> > change to always visit pointer target and function result
>> > and argument types.
>> >
>>
>> This caused:
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49013
>
> I have reverted the patch for now.
>
It doesn't solve the problem and I reopened:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49013
Your followup patches may have similar issues.
--
H.J.
next prev parent reply other threads:[~2011-05-17 13:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 15:46 Richard Guenther
2011-05-17 3:13 ` H.J. Lu
2011-05-17 13:03 ` Richard Guenther
2011-05-17 15:32 ` H.J. Lu [this message]
2011-05-17 15:33 ` H.J. Lu
2011-05-17 15:52 ` Richard Guenther
2011-05-17 16:04 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2011-05-19 14:39 Richard Guenther
2011-05-16 17:09 Richard Guenther
2011-05-16 20:51 ` Jan Hubicka
2011-05-16 22:39 ` H.J. Lu
2011-05-17 11:41 ` Richard Guenther
2011-05-17 13:54 ` Jan Hubicka
2011-05-16 15:36 Richard Guenther
2011-05-13 15:00 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=BANLkTinsamHOGi6VsgjsJTQTGtsQ0EMoig@mail.gmail.com \
--to=hjl.tools@gmail.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).