https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102059
--- Comment #30 from Kewen Lin <linkw at gcc dot gnu.org> --- (In reply to pc from comment #27) > There was a commit related to this bug, but it is still in ASSIGNED state, > so I'm not sure if this was to be considered "fixed", but... > > Chip discovered that, with a build of today's trunk, the original test case, > and at least gcc.target/powerpc/pr102059-1.c still fail (I didn't try > others), and it seems to be related to the presence of "-flto": > -- > $ gcc -c gcc/testsuite/gcc.target/powerpc/pr102059-1.c -O2 -mcpu=power8 > -Wno-attributes -flto > gcc/testsuite/gcc.target/powerpc/pr102059-1.c: In function 'bar': > gcc/testsuite/gcc.target/powerpc/pr102059-1.c:8:1: error: inlining failed in > call to 'always_inline' 'foo': target specific option mismatch > 8 | foo (int *b) > | ^~~ > gcc/testsuite/gcc.target/powerpc/pr102059-1.c:18:8: note: called from here > 18 | *a = foo (a); > | ^~~~~~~ > > $ gcc -c gcc/testsuite/gcc.target/powerpc/pr102059-1.c -O2 -mcpu=power8 > -Wno-attributes > $ > -- > > The testcases included with the commit do not use "-flto", so these tests > are PASSing. Your spotted failure is expected, as comment 25 there are two patches for this issue, the pushed commit was just for the 2nd issue. The first issue is pending on review. Please see the link: https://gcc.gnu.org/pipermail/gcc-patches/2022-January/587635.html, I just ping-ed it before my vacation, will ping it again later.
