From: Jeff Law <law@redhat.com>
To: Vladimir Makarov <vmakarov@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: patch for PR61578
Date: Thu, 24 Sep 2015 23:29:00 -0000 [thread overview]
Message-ID: <5604695D.6060402@redhat.com> (raw)
In-Reply-To: <56045FF8.6070106@redhat.com>
On 09/24/2015 02:41 PM, Vladimir Makarov wrote:
> The following patch solves the 2nd case of
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61578
>
> I did a lot of benchmarking of different heuristics in hard reg cost
> propagation in IRA. This is the best what I found. The patch improves
> stably code size of SPEC2000 and its score although it is not that
> significant.
Didn't we have a handful of missed optimization BZs that we speculated
might be helped by propagation of hard register costs? Might not be a
bad idea to review those and see if any are magically fixed now.
jeff
next prev parent reply other threads:[~2015-09-24 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 22:28 Vladimir Makarov
2015-09-24 23:29 ` Jeff Law [this message]
2015-09-25 17:01 ` Jeff Law
2015-09-25 17:59 ` Vladimir Makarov
-- strict thread matches above, loose matches on Subject: below --
2015-09-01 19:39 Vladimir Makarov
2015-09-02 15:32 ` Christophe Lyon
2015-09-03 15:03 ` Vladimir Makarov
2015-09-03 18:42 ` Vladimir Makarov
2015-09-04 8:40 ` Christophe Lyon
2015-09-23 14:06 ` Dominik Vogt
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=5604695D.6060402@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@redhat.com \
/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).