https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113
--- Comment #22 from Douglas Mencken <dougmencken at gmail dot com> --- So yet I have fully workin’ $ /Developer/GCC/7.3patched/PowerPC/32bit/bin/gcc -v Using built-in specs. COLLECT_GCC=/Developer/GCC/7.3patched/PowerPC/32bit/bin/gcc COLLECT_LTO_WRAPPER=/Developer/GCC/7.3patched/PowerPC/32bit/libexec/gcc/powerpc-unknown-darwin/7.3.0/lto-wrapper Target: powerpc-unknown-darwin Configured with: ../gcc-git/configure --build=powerpc-unknown-darwin --host=powerpc-unknown-darwin --target=powerpc-unknown-darwin --prefix=/Developer/GCC/7.3patched/PowerPC/32bit --enable-languages=c,c++,objc,obj-c++ --enable-shared --enable-static --enable-checking=release --enable-threads=posix --with-__thread --without-system-zlib --disable-nls --disable-werror Thread model: posix gcc version 7.3.0 (GCC) as for https://gcc.gnu.org/ml/gcc-patches/2016-08/msg02040.html I think that optimizing epilogues is a good idea, but not of a cost of unbuildability, even when it’s unbuildability on “quartiary” ( read as “we don’t care” ) platform
