From: Martin Jambor <mjambor@suse.cz>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org, qemu-devel@nongnu.org,
jamborm@gcc.gnu.org, hubicka@ucw.cz
Subject: Re: [Qemu-devel] [PATCH] PR/66760, ipa-inline-analysis.c compile-time hog
Date: Mon, 13 Jul 2015 13:55:09 +0200 [thread overview]
Message-ID: <20150713115509.GG1819@virgil.suse.cz> (raw)
In-Reply-To: <1436737195-21165-1-git-send-email-bonzini@gnu.org>
Hi,
On Sun, Jul 12, 2015 at 11:39:55PM +0200, Paolo Bonzini wrote:
> From: bonzini@gnu.org
>
> In this PR, a lot of time is spent doing the same ipa_load_from_parm_agg
> query over and over. Luckily a memoization scheme is already there, it's
> just not used by ipa-inline-analysis.c. The patch moves the cache struct
> (struct func_body_info) to ipa-prop.h and modify ipa-inline-analysis.c.
> On some testcases from PR26854 the "alias stmt walking" timevar goes
> off the profile while it used to be 30-70%.
>
> Bootstrapped (regtest in progress) on x86_64-pc-linux-gnu.
>
> Please commit the patch for me if approved, as I don't have anymore
> the key I used to use for gcc.gnu.org. One of these days I'll send
> my new SSH public key to the overseers.
I can't approve it, but FWIW, I'm generally fine with the patch.
Although the original idea was to share one func_body_info in between
ipa-cp and ipa-inline analyses, this is certainly better than what we
have now and perhaps even good enough generally.
The only semi-issue I have is the name of func_body_info. If it is
going to be exposed in a header file, perhaps it should get an ipa_
prefix. I also think that its initialization should be put into a
common function, but that is somethig I can do as a followup, if need
be.
In any event, thanks for working on this,
Martin
prev parent reply other threads:[~2015-07-13 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 21:39 [Qemu-devel] [PATCH] PR/66760, ipa-inline-analysis.c compile-time hog Paolo Bonzini
2015-07-13 11:55 ` Martin Jambor [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=20150713115509.GG1819@virgil.suse.cz \
--to=mjambor@suse.cz \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jamborm@gcc.gnu.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).