On Wed, Sep 1, 2021 at 7:24 PM Tamar Christina via Gcc <gcc@gcc.gnu.org> wrote: > > -- edit, added list back in -- > > Just to add some AArch64 numbers for Spec2017 we see 2.1% overall Geomean > improvements (all from x264 as expected) with no real regressions (everything > within variance) and only a 0.06% binary size increase overall (of which x264 > grew 0.15%) using the very cheap cost model. > > So we'd be quite keen on this as well. > > Cheers, > Tamar > > > -----Original Message----- > > From: Gcc <gcc-bounces+tamar.christina=arm....@gcc.gnu.org> On Behalf > > Of Florian Weimer via Gcc > > Sent: Monday, August 30, 2021 2:05 PM > > To: gcc@gcc.gnu.org > > Cc: ja...@redhat.com; Richard Earnshaw <richard.earns...@arm.com>; > > Segher Boessenkool <seg...@kernel.crashing.org>; Richard Sandiford > > <richard.sandif...@arm.com>; premachandra.malla...@amd.com; > > Hongtao Liu <hongtao....@intel.com> > > Subject: Enable the vectorizer at -O2 for GCC 12 > > > > 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? > > > > Thanks, > > Florian >
A patch is posted at [1] to enable auto-vectorization at O2 w/ very-cheap cost mode. [1] https://gcc.gnu.org/pipermail/gcc-patches/2021-September/578877.html -- BR, Hongtao
