From: "Kewen.Lin" <linkw@linux.ibm.com>
To: wschmidt@linux.ibm.com, Florian Weimer <fweimer@redhat.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>, "H.J. Lu" <hjl.tools@gmail.com>,
Hongtao Liu <hongtao.liu@intel.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
jakub@redhat.com, rearnsha@arm.com, richard.sandiford@arm.com,
Premachandra.Mallappa@amd.com, gcc@gcc.gnu.org
Subject: Re: Enable the vectorizer at -O2 for GCC 12
Date: Tue, 31 Aug 2021 11:10:44 +0800 [thread overview]
Message-ID: <2ab5dd7f-3170-a0fc-e3e4-6376510f89ea@linux.ibm.com> (raw)
In-Reply-To: <0e35169d-b9df-f665-dbc1-a3e76a3e7d8e@linux.ibm.com>
on 2021/8/30 下午10:11, Bill Schmidt wrote:
> On 8/30/21 8:04 AM, Florian Weimer wrote:
>> There has been a discussion, both off-list and on the gcc-help mailing
>> list (“Why vectorization didn't turn on by -O2”, spread across several
>> months), about enabling the auto-vectorizer at -O2, similar to what
>> Clang does.
>>
>> I think the review concluded that the very cheap cost model should be
>> used for that.
>>
>> Are there any remaining blockers?
>
> Hi Florian,
>
> I don't think I'd characterize it as having blockers, but we are continuing to investigate small performance issues that arise with very-cheap, including some things that regressed in GCC 12. Kewen Lin is leading that effort. Kewen, do you feel we have any major remaining concerns with this plan?
>
Hi Florian & Bill,
There are some small performance issues like PR101944 and PR102054, and
still two degraded bmks (P9 520.omnetpp_r -2.41% and P8 526.blender_r
-1.31%) to be investigated/clarified, but since their performance numbers
with separated loop and slp vectorization options look neutral, they are
very likely noises. IMHO I don't think they are/will be blockers.
So I think it's good to turn this on by default for Power.
BR,
Kewen
next prev parent reply other threads:[~2021-08-31 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 13:04 Florian Weimer
2021-08-30 14:11 ` Bill Schmidt
2021-08-31 3:10 ` Kewen.Lin [this message]
2021-08-31 3:30 ` Hongtao Liu
2021-08-31 4:13 ` Jeff Law
2021-09-01 9:10 ` Andrew Stubbs
2021-09-01 11:23 ` Tamar Christina
2021-09-06 9:04 ` Hongtao Liu
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=2ab5dd7f-3170-a0fc-e3e4-6376510f89ea@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=Premachandra.Mallappa@amd.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hongtao.liu@intel.com \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=rearnsha@arm.com \
--cc=richard.sandiford@arm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.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).