]> git.ipfire.org Git - thirdparty/gcc.git/commitdiff
cray_pointers_2.f90: Avoid cycling through optimization options.
authorRainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Mon, 24 Jan 2011 12:21:14 +0000 (12:21 +0000)
committerRainer Orth <ro@gcc.gnu.org>
Mon, 24 Jan 2011 12:21:14 +0000 (12:21 +0000)
* gfortran.dg/cray_pointers_2.f90: Avoid cycling through
optimization options.

From-SVN: r169158

gcc/testsuite/ChangeLog
gcc/testsuite/gfortran.dg/cray_pointers_2.f90

index f22cc246d477a87263d9b7ba66f3dcb461e7ef0a..4537858751c5b0cf3de123cfb69549d247914d8f 100644 (file)
@@ -1,3 +1,8 @@
+2011-01-24  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
+
+       * gfortran.dg/cray_pointers_2.f90: Avoid cycling through
+       optimization options.
+
 2011-01-24  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
 
        * gfortran.dg/array_constructor_33.f90: Use dg-timeout-factor 4.
index cbebad6addfda7535c0b0e1cfe42a7ef0c22cdeb..049b08c02f05e8dc9f299690b1addd56e9bd497a 100644 (file)
@@ -1,5 +1,7 @@
-! { dg-do run }
-! { dg-options "-fcray-pointer -fbounds-check" }
+! 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-options "-O3 -fcray-pointer -fbounds-check" }
 ! { dg-timeout-factor 4 }
 ! Series of routines for testing a Cray pointer implementation
 program craytest