https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67295
--- Comment #3 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- Still no luck on a x86_64-linux-gnu build machine, running ../configure --target=arm-none-eabi --disable-shared --disable-nls --disable-threads --disable-tls --enable-checking=yes --enable-languages=c,c++,fortran --with-newlib --with-fpu=neon-fp-armv8 --with-arch=armv8-a --without-isl building binutils (+gdb commit db1ff28b60) and newlib (+cygwin commit c7806ef76a) on the same tree. I'm afraid this is going to be very hard to debug if I can't duplicate it. Any chance you could build a toolchain that works on some machine on the gcc build farm, so that I could get access to it as well and debug from there, or at least try to figure out what the differences are between our setups? Thanks,
