[Bug fortran/27766] [meta] -fbounds-check related bugs

[dominiq at lps dot ens dot fr]

------- Comment #10 from dominiq at lps dot ens dot fr  2008-11-23 22:39 -------
With the following changes:

Only in ../_gcc_clean/gcc/testsuite/gfortran.dg/: array_memset_2.f90
Only in gcc/testsuite/gfortran.dg/: array_setmem_2.f90

--- ../_gcc_clean/gcc/testsuite/gfortran.dg/pr37243.f   2008-09-04
19:10:20.000000000 +0200
+++ gcc/testsuite/gfortran.dg/pr37243.f 2008-11-23 22:54:23.000000000 +0100
@@ -34,7 +34,7 @@
       IF (J .GT. N) GO TO 320
       DO 240 K = 1,N
   240 V(K,I) = ZERO
-      CALL DAXPY(N,DUM,V(1,II),1,V(1,I),1)
+      CALL DAXPY(N,DUM,V(1,I),1,V(1,I),1)
   260 CONTINUE
       DUMI = ZERO
       DO 280 K = 1,N

--- ../_gcc_clean/gcc/testsuite/gfortran.dg/g77/dnrm2.f 2007-11-07
10:25:55.000000000 +0100
+++ gcc/testsuite/gfortran.dg/g77/dnrm2.f       2008-11-23 22:53:37.000000000
+0100
@@ -26,7 +26,7 @@

       double precision function dnrm2 ( n, dx, incx)
       integer i, incx, ix, j, n, next
-      double precision   dx(1), cutlo, cuthi, hitest, sum, xmax,zero,one
+      double precision   dx(n), cutlo, cuthi, hitest, sum, xmax,zero,one
       data   zero, one /0.0d0, 1.0d0/
       data cutlo, cuthi / 8.232d-11,  1.304d19 /
       j = 0

I only get the following failures with -fbounds-check:

FAIL: gfortran.dg/forall_13.f90  -O0  execution test
FAIL: gfortran.dg/forall_13.f90  -O1  execution test
FAIL: gfortran.dg/forall_13.f90  -O2  execution test
FAIL: gfortran.dg/forall_13.f90  -O3 -fomit-frame-pointer  execution test
FAIL: gfortran.dg/forall_13.f90  -O3 -fomit-frame-pointer -funroll-loops 
execution test
FAIL: gfortran.dg/forall_13.f90  -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions  execution test
FAIL: gfortran.dg/forall_13.f90  -O3 -g  execution test
FAIL: gfortran.dg/forall_13.f90  -Os  execution test
FAIL: gfortran.dg/ldist-1.f90  -O  scan-tree-dump-times ldist "distributed:
split to 4 loops" 1
FAIL: gfortran.dg/ltrans-7.f90  -O  scan-tree-dump-times ltrans "transformed
loop" 1
FAIL: gfortran.dg/reassoc_4.f  -O  scan-tree-dump-times reassoc1 "[0-9] \* " 22
FAIL: gfortran.dg/vect/vect-3.f90  -O  scan-tree-dump-times vect "Alignment of
access forced using peeling" 1
FAIL: gfortran.dg/vect/vect-3.f90  -O  scan-tree-dump-times vect "Vectorizing
an unaligned access" 1
FAIL: gfortran.dg/vect/vect-5.f90  -O  scan-tree-dump-times vect "vectorized 1
loops" 1
FAIL: gfortran.dg/vect/vect-5.f90  -O  scan-tree-dump-times vect "Alignment of
access forced using peeling" 1
FAIL: gfortran.dg/vect/vect-5.f90  -O  scan-tree-dump-times vect "Vectorizing
an unaligned access" 1
FAIL: gfortran.dg/vect/pr19049.f90  -O  scan-tree-dump-times vect "complicated
access pattern" 1

So, but for pr36091, the failures are expected regexps changed by
-fbounds-check which is not too surprising.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27766