On Thu, Aug 18, 2022 at 12:13 AM Thorsten Glaser <t...@mirbsd.de> wrote:
>
> Arnd Bergmann dixit:
>
> >The way the FPU type gets selected in gcc changed with recent versions,
> >this was intentional and won't be reverted but it did break packages that
> >used the old method.
>
> Hmph.
>
> >In most cases, it's sufficient to pass
> >-march=armv7-a+fp instead of -march=armv7-a to pick the right
> >instruction set.
>
> There’s no “instead of”, though.
>
> So basically, I now need to add -march=… to CFLAGS in the package
> when compiling for either of armel and armhf.
What I see with gcc-12-arm-linux-gnueabihf 12.1.0-8cross1 is that it defaults
to the correct architecture level (armv7-a+fp) and passes that to the assembler,
so it /should/ not be necessary do this explictily.
The problem with other packages was that they did pass "-march=armv7-a"
for armhf, but that is interpreted as not having an FPU now, where on older
compilers the -mhard-float flag would override the -march= flag and enable
support for an FPU regardless.
> Which value do I use for armel, which for armhf (the one you gave
> is for armhf, I think)?
That should be -march=armv5te
Arnd
