This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/31119] -fbounds-check: Check for presence of optional arguments before bound checking
- From: "hubicka at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 20 Oct 2012 14:38:05 +0000
- Subject: [Bug fortran/31119] -fbounds-check: Check for presence of optional arguments before bound checking
- Auto-submitted: auto-generated
- References: <bug-31119-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31119
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #7 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-10-20 14:38:05 UTC ---
Hi,
can someone fortran aware please double-check that the tests
* gfortran.dg/bounds_check_9.f90: New test.
* gfortran.dg/bounds_check_fail_2.f90: New test.
do not contain out of bounds access? I am working on path to bound number of
loop iterations better based on array accesses and what I see is array A.9
containing values {1,2} that is accessed in the loop header.
We bound number of iterations of that loop to 1 (that is one loopback edge
iteration to walk both parts of the array) and then the testcases start
failing.
I do not understand the testcase.
Perhaps the bounds-check instrumentation happens too late or we need to disable
this logic with -fbounds-check?
Honza