On Wed, Jun 29, 2022 at 5:34 PM Wookey <[email protected]> wrote: [...] > The reason this has broken appears to be that gcc has changed the way > the fpu is specified/defaulted, so neon _and_ fp are enabled by > default if no specific fpu option is given. (i.e we just set > -march=armv7). It used to be that -march=armv7 implied +nosimd. (or > something like that - I never quite got to the bottom of it enough to > be sure eactly what the right general or specific fix was). > > If you rebuild with > -march=armv7-a+nosimd+nofp > or > -march=armv7-a+nosimd+fp > you should be able to determine if being more explicit about the fp and > simd(neon) instructions used makes it behave.
This has been reported as: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014091 Thanks
