https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124819
--- Comment #3 from anlauf at gcc dot gnu.org --- (In reply to Christopher Albert from comment #2) > I tested other compilers on the same system and libc. > > Results: > - system gfortran 15.2.1: passes > - nvfortran 26.3: passes > - local GCC 16 object linked against system libgfortran: passes > - system gfortran object linked against local GCC 16 libgfortran: fails > > So the failure follows the local libgfortran, not the frontend or glibc > alone. That points directly at the GCC 16 libgfortran transformational > REAL(4) BESSEL_JN runtime path. The only difference I see then is the CFLAGS. (I use "-g -march=native -O2" on an Intel i5-8250U and also compile with --disable-bootstrap.)
