https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93384
--- Comment #15 from Peter Bergner <bergner at gcc dot gnu.org> --- So using the configure setup (minus the -specs=... options) in Comment 13, I was able to recreate the issue using unpatched Python-3.9.0a3 and GCC10. The failing command is: /home/bergner/gcc/install/gcc-fsf-mainline-base/libexec/gcc/powerpc64le-linux/10.0.1/lto1 -quiet -dumpdir ./ -dumpbase libpython3.9.a -mcpu=power8 -mtune=power8 -m64 -auxbase-strip libpython3.9.so.lto.o -g -O2 -version -fno-openmp -fno-openacc -fPIC -fuse-linker-plugin -ffat-lto-objects -flto-partition=none -fno-semantic-interposition -flinker-output=dyn @/tmp/ccikqTcI -o getbuildinfo.s I notice if I drop the -fno-semantic-interposition option, I only get 1: .set _PyObject_AssertFailed.localalias,_PyObject_AssertFailed instead of 2.