From: Pat Haugen <pthaugen@linux.vnet.ibm.com>
To: Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH][v4] GIMPLE store merging pass
Date: Thu, 29 Sep 2016 16:01:00 -0000 [thread overview]
Message-ID: <bb5da962-4ddc-1c3f-e0ac-55b7f2829749@linux.vnet.ibm.com> (raw)
In-Reply-To: <0BED6BB0-4196-4086-919E-EEDDA5923FFF@linux.vnet.ibm.com>
On 09/28/2016 10:59 AM, Bill Schmidt wrote:
>> Bill, could you or someone else with access to Power benchmarking try this patch out on some benchmarks
>> > that you usually use? The new pass in this patch is on by default and can be turned off by -fno-store-merging
>> > if needed. Jakub indicated that his last attempt at this work caused regressions on powerpc so I'd like to
>> > see if this patch is okay in that regard.
> Hi Kyrill,
>
> Thanks for the heads-up! I will have someone on my team look at this as soon as possible.
>
I tried the patch on SPEC2006 on powerpc64le and the results were neutral, no noticeable improvements or degradations.
-Pat
next prev parent reply other threads:[~2016-09-29 15:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 16:00 Kyrill Tkachov
2016-09-28 16:07 ` Bill Schmidt
2016-09-28 16:09 ` Kyrill Tkachov
2016-09-29 16:01 ` Pat Haugen [this message]
2016-09-29 16:10 ` Kyrill Tkachov
2016-09-28 17:32 ` Pat Haugen
2016-09-29 8:02 ` Richard Biener
2016-09-29 8:24 ` Kyrill Tkachov
2016-09-29 10:54 ` Richard Biener
2016-09-29 15:37 ` Kyrill Tkachov
2016-09-30 7:09 ` Richard Biener
2016-09-30 15:25 ` Kyrill Tkachov
2016-09-30 15:34 ` Kyrill Tkachov
2016-09-30 17:02 ` Richard Biener
2016-09-30 16:58 ` Kyrill Tkachov
2016-10-04 8:18 ` Richard Biener
2016-10-03 13:02 ` Kyrill Tkachov
2016-10-03 16:43 ` Richard Biener
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=bb5da962-4ddc-1c3f-e0ac-55b7f2829749@linux.vnet.ibm.com \
--to=pthaugen@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=rguenther@suse.de \
--cc=wschmidt@linux.vnet.ibm.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).