https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107413
--- Comment #16 from Rama Malladi <rvmallad at amazon dot com> --- (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 fp 1-copy rate Ratio 503.bwaves_r 0.98 507.cactuBSSN_r 1.00 508.namd_r 0.97 510.parest_r NA 511.povray_r NA 519.lbm_r 1.16 521.wrf_r 1.00 526.blender_r 0.99 527.cam4_r NA 538.imagick_r 1.17 544.nab_r 1.01 549.fotonik3d_r NA 554.roms_r 1.00 geomean 1.03