https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67295
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-11-07 CC| |ramana at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #4 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> --- (In reply to Alexandre Oliva from comment #3) > 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, I can see that this is a regression from GCC 5 - however something is fishy here. Is there a chance Kyrill and you have different --enable-checking options ?