From: Jan Hubicka <hubicka@ucw.cz>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Richard Guenther <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][4/n] Cleanup LTO type merging
Date: Thu, 12 May 2011 14:50:00 -0000 [thread overview]
Message-ID: <20110512113901.GA16940@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20110511222035.GA1861@atrey.karlin.mff.cuni.cz>
> >
> > This removes the mode param from the generic type merging machinery
> > and simplifies code accordingly.
> >
> > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
> Hi,
> looks the cleanup series makes a progress, now I get 459s for Mozilla WPA (it was 540 last time I tried).
> Out of that 262s is still ipa lto decl in.
> oprofile is as follows:
>
> 123230 20.1719 lto1 htab_find_slot_with_hash
> 58203 9.5274 lto1 gimple_type_eq
> 50017 8.1874 lto1 iterative_hash_hashval_t
> 40099 6.5639 libc-2.11.1.so _int_malloc
^^ note that the int_malloc calls seems to be mostly due to repetetive creating/destroying the scc pointer map.
Honza
prev parent reply other threads:[~2011-05-12 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 14:07 Richard Guenther
2011-05-12 8:41 ` Jan Hubicka
2011-05-12 14:50 ` Jan Hubicka [this message]
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=20110512113901.GA16940@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--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).