-- 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 <[email protected]> On Behalf > Of Florian Weimer via Gcc > Sent: Monday, August 30, 2021 2:05 PM > To: [email protected] > Cc: [email protected]; Richard Earnshaw <[email protected]>; > Segher Boessenkool <[email protected]>; Richard Sandiford > <[email protected]>; [email protected]; > Hongtao Liu <[email protected]> > 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
