From: Richard Guenther <richard.guenther@gmail.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: David Edelsohn <dje.gcc@gmail.com>, Steve Ellcey <sje@cup.hp.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Ping: IRA-based register pressure calculation for RTL loop invariant motion
Date: Tue, 20 Oct 2009 09:29:00 -0000 [thread overview]
Message-ID: <84fc9c000910200227s685fc1d3w16fea2149790dde5@mail.gmail.com> (raw)
In-Reply-To: <4ADD2542.1040401@redhat.com>
On Tue, Oct 20, 2009 at 4:49 AM, Vladimir Makarov <vmakarov@redhat.com> wrote:
> David Edelsohn wrote:
>>
>> On Mon, Oct 19, 2009 at 12:17 PM, Vladimir Makarov <vmakarov@redhat.com>
>> wrote:
>>
>>
>>>>
>>>> I think we could switch it on by default at -O3 for a selected group of
>>>> targets. Itanium overall also improves with the new heuristics. That
>>>> would
>>>> make it power and Itanium.
>>>>
>>>
>>> The patch is below. Ok to commit?
>>>
>>>>
>>>> Did you try restricting the heuristics to certain
>>>> register classes, like SSE registers on x86_64?
>>>>
>>>>
>>>>
>>>
>>> No, I did not try. I am not sure it is worth to do it.
>>>
>>>
>>> 2009-10-19 Vladimir Makarov <vmakarov@redhat.com>
>>>
>>> * doc/invoke.texi (fira-loop-pressure): Update default value.
>>> * opts.c (decode_options): Remove default value setting for
>>> flag_ira_loop_pressure.
>>> * config/ia64/ia64.c (ia64_override_options): Set
>>> flag_ira_loop_pressure up for -O3.
>>> * config/rs6000/rs6000.c (rs6000_override_options): Ditto.
>>>
>>
>> Tests inside IBM do not show this IRA feature as an overall win for
>> POWER. If we figure out and fix why artificially limiting
>> rs6000_issue_rate to 1 for the first scheduler pass still helps (and
>> it does), then this would make sense. Until then, please do not apply
>> this patch to rs6000.
>>
>>
>
> David, I think there is some misunderstanding. It is a different patch.
> You are probably talking about register pressure sensitive insn scheduling
> (by the way I am still working on its tuning). This patch is about more
> accurate register pressure calculation to decide profitability to do RTL
> loop invariant motion. SPEC2000 and polyhedron benchmarks for power6 shows
> that this patch is a clear win. You could test and benchmark this patch
> internally in IBM to confirm or deny my observation if you wish.
The non-powerpc pieces of the patch are ok.
Thanks,
Richard.
next prev parent reply other threads:[~2009-10-20 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 3:19 Vladimir Makarov
2009-10-01 8:49 ` Zdenek Dvorak
2009-10-01 14:34 ` Vladimir Makarov
2009-10-14 15:21 ` Zdenek Dvorak
2009-10-14 16:36 ` Vladimir Makarov
2009-10-16 21:58 ` Richard Guenther
2009-10-17 5:32 ` Vladimir Makarov
2009-10-17 11:17 ` Richard Guenther
2009-10-19 16:21 ` Vladimir Makarov
2009-10-20 2:54 ` David Edelsohn
2009-10-20 3:39 ` Vladimir Makarov
2009-10-20 9:29 ` Richard Guenther [this message]
2009-10-20 14:42 ` David Edelsohn
2009-10-13 22:25 ` Ping 2: " Vladimir Makarov
2009-10-14 9:48 ` 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=84fc9c000910200227s685fc1d3w16fea2149790dde5@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sje@cup.hp.com \
--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).