https://gcc.gnu.org/g:22f4125f19d58e30997518e22dfe0bae7cdbbcb6
commit r15-8983-g22f4125f19d58e30997518e22dfe0bae7cdbbcb6
Author: Sam James <s...@gentoo.org>
Date: Thu Mar 27 17:52:19 2025 +0000
testsuite: revert Fortran change
Revert part of my change from r15-8973-g1307de1b4e7d5e; as Harald points
out, the comment explains why this is there. It's a hack but it needs to
stay for now. (I did have this marked as a TODO in my branch and didn't
leave a proper note as to why, so it's my fault.)
gcc/testsuite/ChangeLog:
* gfortran.dg/cray_pointers_2.f90: Restore whitespace.
Diff:
---
gcc/testsuite/gfortran.dg/cray_pointers_2.f90 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/gfortran.dg/cray_pointers_2.f90
b/gcc/testsuite/gfortran.dg/cray_pointers_2.f90
index a7e15bad850a..4351874825ed 100644
--- a/gcc/testsuite/gfortran.dg/cray_pointers_2.f90
+++ b/gcc/testsuite/gfortran.dg/cray_pointers_2.f90
@@ -1,6 +1,6 @@
! Using two spaces between dg-do and run is a hack to keep gfortran-dg-runtest
! from cycling through optimization options for this expensive test.
-! { dg-do run }
+! { dg-do run }
! { dg-options "-O3 -fcray-pointer -fbounds-check -fno-inline" }
! { dg-timeout-factor 4 }
!
