https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71399
--- Comment #19 from wilco at gcc dot gnu.org --- (In reply to Jeffrey A. Law from comment #18) > I've been able to reproduce this under arm-qemu. > > Start by bootstrapping and installing gcc-4.9.4. Then use that gcc-4.9.4 to > build gcc-5.3.0 and you'll get the comparison failure. > > Based on various comments I strongly suspect this is a bug in gcc-4.9.4. Yes, the (In reply to Jeffrey A. Law from comment #18) > I've been able to reproduce this under arm-qemu. > > Start by bootstrapping and installing gcc-4.9.4. Then use that gcc-4.9.4 to > build gcc-5.3.0 and you'll get the comparison failure. > > Based on various comments I strongly suspect this is a bug in gcc-4.9.4. Yes we know the bug is still in 4.9.4, but that branch has been closed. It's fixed everywhere else. Simple workarounds for 4.9.4 are -mneon-for-64bits, -marm or -mfpu=vfpv4.
