This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Regression on mainline
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Sat, 3 Jul 2004 11:58:02 -0700
- Subject: Regression on mainline
A commit made on June 30th has lead to the following
regression in gfortran.
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -O0
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -O1
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -O2
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -O2 -fno-repack-arrays
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -O3 -g
FAIL: gfortran.fortran-torture/execute/intrinsic_nearest.f90 execution, -Os
AFAICT, the commit causing the problem was not to the gfortran
frontend or its runtime library, libgfortran. I believe a change
to the middle end or back end is the culprit, but I have only been
able to narrow down the problem to a June 30th commit.
--
Steve