https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94694
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note in another bug it was said that libgfortran requires a C99 runtime, when
that's not available you should disable gfortran build. GCC (or libgfortran)
is in no position to disable parts of its features and AFAICS for QOI issues
the _frontend_ would need to reject programs making use of disabled library
functionality, otherwise programs are going to only fail to link.
IMHO failure at runtime when the disabled functionality is actually invoked
isn't good QOI either.
Re-implementing missing functions in libgfortran isn't trivial either.
Since Fortran isn't release critical the only P1-ish part is that fortran
build is enabled on aarch64-elf and thus we can resolve this by adding
aarch64-elf-*) to
# Disable Fortran for some systems.
case "${target}" in
mmix-*-*)
# See <http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00572.html>.
unsupported_languages="$unsupported_languages fortran"
;;
bpf-*-*)
unsupported_languages="$unsupported_languages fortran"
;;
esac
technically aarch64-elf isn't a primary architecture.
