public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bill Schmidt <wschmidt@linux.ibm.com>
To: Florian Weimer <fweimer@redhat.com>, gcc@gcc.gnu.org
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, "Kewen.Lin" <linkw@linux.ibm.com>
Subject: Re: Enable the vectorizer at -O2 for GCC 12
Date: Mon, 30 Aug 2021 09:11:26 -0500	[thread overview]
Message-ID: <0e35169d-b9df-f665-dbc1-a3e76a3e7d8e@linux.ibm.com> (raw)
In-Reply-To: <87v93nozh7.fsf@oldenburg.str.redhat.com>

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?

Thanks,
Bill

>
> Thanks,
> Florian
>

  reply	other threads:[~2021-08-30 14: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 [this message]
2021-08-31  3:10   ` Kewen.Lin
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=0e35169d-b9df-f665-dbc1-a3e76a3e7d8e@linux.ibm.com \
    --to=wschmidt@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=linkw@linux.ibm.com \
    --cc=rearnsha@arm.com \
    --cc=richard.sandiford@arm.com \
    --cc=segher@kernel.crashing.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 read-only IMAP folder(s) and NNTP newsgroup(s).