https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83206
--- Comment #8 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- (In reply to Andrew Roberts from comment #7) > I get the same thing if I just use -mcpu=native: > > /usr/local/gcc/bin/gcc -o matrix-v6 -mcpu=native -mfpu=auto -O3 matrix.c > cc1: error: -mfloat-abi=hard: selected processor lacks an FPU > Ok, I'll look a bit further. > I realize the aarch64 compiler does not need -mfpu=auto, but I was wondering > if it was worth at least not rejecting it so makefiles can be portable > between arm and aarch64. At present you get: > > gcc: error: unrecognized command line option ‘-mfpu=auto’ > No, that would be a bad idea. -mfpu=auto is supposed to be a transition path to making the -mfpu option obsolete (ie doing the way we do things on AArch64). Adding that to the aarch64 compiler would be a backwards step. > and the compile fails > > A Rasbperry PI Zero is the cheapest and easiest armv6 option, although it > does take 24hrs to build the compiler
