mattst88 :gentoo:<p>I also tried and couldn't reproduce the failure in a 32-bit chroot on <a href="https://fosstodon.org/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gentoo</span></a>'s <a href="https://fosstodon.org/tags/aarch64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>aarch64</span></a> development machine, so I was stuck doing all the debugging (and loooooong <a href="https://fosstodon.org/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gcc</span></a> builds) on my very slow single-core 800MHz Solid Run <a href="https://fosstodon.org/tags/CuBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CuBox</span></a>.</p><p>Diff'ing the assembly output between the non-working and working gcc versions I saw:</p><p>> - vmov.f64 d0, #6.:e+0<br>> + vmov.f64 d0, #7.0e+0</p><p>Naturally, binutils' assembler fails to recognize "6.:e+0" as a floating-point constant. Where is the ":" coming from?</p>