public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/57721] New: wrong error message with bounds checking.
@ 2013-06-26  9:26 Joost.VandeVondele at mat dot ethz.ch
  2013-06-26 10:32 ` [Bug fortran/57721] " dominiq at lps dot ens.fr
  2013-06-26 10:43 ` burnus at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: Joost.VandeVondele at mat dot ethz.ch @ 2013-06-26  9:26 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 57721
           Summary: wrong error message with bounds checking.
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Joost.VandeVondele at mat dot ethz.ch

The following testcase:

> cat test.f90 
TYPE data
  INTEGER :: x(10)
END TYPE
TYPE data_areas
  TYPE(data) :: y(10)
END TYPE

TYPE(data_areas) :: z(10)

integer, volatile :: i,j,k
i=1 ; j=1 ; k=11

z(i)%y(j)%x(k)=0

END


> gfortran -fbounds-check test.f90 ; ./a.out
At line 13 of file test.f90
Fortran runtime error: Index '11' of dimension 1 of array 'z' above upper bound
of 10


detects the out-of-bounds access, but mentions the incorrect 'z' instead of the
correct 'x'


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug fortran/57721] wrong error message with bounds checking.
  2013-06-26  9:26 [Bug fortran/57721] New: wrong error message with bounds checking Joost.VandeVondele at mat dot ethz.ch
@ 2013-06-26 10:32 ` dominiq at lps dot ens.fr
  2013-06-26 10:43 ` burnus at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-06-26 10:32 UTC (permalink / raw)
  To: gcc-bugs

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-06-26
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed. I also see the same thing with 4.4.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug fortran/57721] wrong error message with bounds checking.
  2013-06-26  9:26 [Bug fortran/57721] New: wrong error message with bounds checking Joost.VandeVondele at mat dot ethz.ch
  2013-06-26 10:32 ` [Bug fortran/57721] " dominiq at lps dot ens.fr
@ 2013-06-26 10:43 ` burnus at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: burnus at gcc dot gnu.org @ 2013-06-26 10:43 UTC (permalink / raw)
  To: gcc-bugs

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |burnus at gcc dot gnu.org
         Resolution|---                         |DUPLICATE

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Duplicate of the old PR 29800.

*** This bug has been marked as a duplicate of bug 29800 ***


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-06-26 10:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-26  9:26 [Bug fortran/57721] New: wrong error message with bounds checking Joost.VandeVondele at mat dot ethz.ch
2013-06-26 10:32 ` [Bug fortran/57721] " dominiq at lps dot ens.fr
2013-06-26 10:43 ` burnus at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).