On 5/25/26 1:04 AM, Haochen Jiang wrote:
On Linux/x86_64,
5d0a9050f3a1c1f9f8e89188dec3d6f39c64a06a is the first bad commit
commit 5d0a9050f3a1c1f9f8e89188dec3d6f39c64a06a
Author: Jerry DeLisle <[email protected]>
Date: Sun May 10 18:13:48 2026 -0700
Fortran: [PR93727] Implement EX format specifier for WRITE
caused
FAIL: gfortran.dg/EXformat_1.F90 -O0 execution test
FAIL: gfortran.dg/EXformat_1.F90 -O1 execution test
FAIL: gfortran.dg/EXformat_1.F90 -O2 execution test
FAIL: gfortran.dg/EXformat_1.F90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/EXformat_1.F90 -O3 -g execution test
FAIL: gfortran.dg/EXformat_1.F90 -Os execution test
FAIL: gfortran.dg/EXformat_2.f90 -O0 execution test
FAIL: gfortran.dg/EXformat_2.f90 -O1 execution test
FAIL: gfortran.dg/EXformat_2.f90 -O2 execution test
FAIL: gfortran.dg/EXformat_2.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/EXformat_2.f90 -O3 -g execution test
FAIL: gfortran.dg/EXformat_2.f90 -Os execution test
with GCC configured with
../../gcc/configure
--prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r17-702/usr
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl
--enable-libmpx x86_64-linux --disable-bootstrap
To reproduce:
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/EXformat_1.F90
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/EXformat_1.F90
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/EXformat_2.f90
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/EXformat_2.f90
--target_board='unix{-m32\ -march=cascadelake}'"
(Please directly reply to this email for question about this report.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
I believe I pushed the fix for this last night, see PR93727.
