http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48477
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2011.04.06 13:04:07
Ever Confirmed|0 |1
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-04-06
13:04:07 UTC ---
Confirm on x86-64-Linux. In a way I am surprised that it does not crash there -
but at least valgrind properly warns.
The issue is:
allocate(B(3)[-4:*])
call three_b(3,B)
...
subroutine three_b(n,A)
integer :: n
integer :: A(-1:3,0:4,-2:5,-4:7)[n+2:n+5,n-1:*]
...
A(1,1,1,1) = 42
Thus, one passes "B" which is a size 3 array as actual argument to a dummy
array "A" which has the size 2400. (That's questionable usage, but still
valid.)
If one now accesses the element A(1,1,1,1) on effectively accesses array
element B(144) which is not that healthy if B has only 3 elements.
