I also tried and couldn't reproduce the failure in a 32-bit chroot on #Gentoo's #aarch64 development machine, so I was stuck doing all the debugging (and loooooong #gcc builds) on my very slow single-core 800MHz Solid Run #CuBox.
Diff'ing the assembly output between the non-working and working gcc versions I saw:
> - vmov.f64 d0, #6.:e+0
> + vmov.f64 d0, #7.0e+0
Naturally, binutils' assembler fails to recognize "6.:e+0" as a floating-point constant. Where is the ":" coming from?
