https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107413
--- Comment #19 from Rama Malladi <rvmallad at amazon dot com> --- (In reply to Wilco from comment #17) > (In reply to Rama Malladi from comment #16) > > (In reply to Wilco from comment #15) > > > (In reply to Rama Malladi from comment #14) > > > > This fix also improved performance of 538.imagick_r by 15%. Did you > > > > have a > > > > similar observation? Thank you. > > > > > > No, but I was using -mcpu=neoverse-n1 as my baseline. It's possible > > > -mcpu=neoverse-v1 shows larger speedups, what gain do you get on the > > > overall > > > FP score? > > > > I was using -mcpu=native and run on a Neoverse V1 arch (Graviton3). Here are > > the scores I got (relative gains of latest mainline vs. an earlier > > mainline). > > > > Latest mainline: 0976b012d89e3d819d83cdaf0dab05925b3eb3a0 > > Earlier mainline: f896c13489d22b30d01257bc8316ab97b3359d1c > > Right that's about 3 weeks of changes, I think > 1b9a5cc9ec08e9f239dd2096edcc447b7a72f64a has improved imagick_r. > > > geomean 1.03 > > That's a nice gain in 3 weeks! Hi Wilco, Could you backport the change to active release branches? Thanks.
