https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70896
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ramana at gcc dot gnu.org
--- Comment #5 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
(In reply to PeteVine from comment #4)
> Until it failed again during the fortran part:
>
> ../../../libgfortran/io/transfer.c: In function ‘bswap_array’:
> ../../../libgfortran/io/transfer.c:915:25: fatal error: You must enable NEON
> instructions (e.g. -mfloat-abi=softfp -mfpu=neon) to use these intrinsics.
> ((uint16_t*)dest)[i] = __builtin_bswap16 (((uint16_t*)src)[i]);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[3]: *** [transfer.lo] Error 1
>
> but that looks like user error. It would be nice if `configure` could abort
> or at least warn on not finding `-mfpu=neon` among CFLAGS if fortran was
> enabled.
>
Strange - that shouldn't be happening and certainly looks like a bug - there
are a number of folks who bootstrap in Thumb mode and --with-fpu=vfpv3-d16
which is essentially the same as vfpv3 but with only 16 D registers.
I'm not sure what's going on here.
