https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91730
Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|powerpc64le-unknown-linux-g |powerpc64le-unknown-linux-g |nu |nu, x86_64-*-* CC| |barnaby.wilks at arm dot com Blocks| |26163 Target Milestone|--- |10.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Using -Ofast I presume? Note there's the 'match' debug-counter you can use to bisect the offending transform (per source file of course). Confirmed on a Haswell machine with -Ofast -march=native as well. Not exactly wrong-code confirmed yet but we'd like to have SPEC CPU "-Ofast clean" and thus need to understand what actual transform is bad here. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163 [Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)