public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/28494]  New: Unclear run time error message
@ 2006-07-26 16:18 schnetter at aei dot mpg dot de
  2006-07-26 16:22 ` [Bug fortran/28494] " pinskia at gcc dot gnu dot org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: schnetter at aei dot mpg dot de @ 2006-07-26 16:18 UTC (permalink / raw)
  To: gcc-bugs

I received the run time error message "upper bound of dimension 1 exceeded".  I
initially thought that I had an array with an upper bound of 1, and that the
array index was larger than that.  I now think that the error message tells me
that I have a rank-2 array, and that the upper bound of the first rank was
exceeded.

The error message could be improved to read "rank 1" or "index 1" instead.


-- 
           Summary: Unclear run time error message
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: schnetter at aei dot mpg dot de


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


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

* [Bug fortran/28494] Unclear run time error message
  2006-07-26 16:18 [Bug fortran/28494] New: Unclear run time error message schnetter at aei dot mpg dot de
@ 2006-07-26 16:22 ` pinskia at gcc dot gnu dot org
  2006-09-20  8:27 ` tobias dot burnus at physik dot fu-berlin dot de
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-07-26 16:22 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from pinskia at gcc dot gnu dot org  2006-07-26 16:22 -------
"dimension 1" means to me, the first dimension.  I don't see why it was not
hard to understand, in fact I did not read the rest of your message until I
already said to myself this was the first dimension.


-- 


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


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

* [Bug fortran/28494] Unclear run time error message
  2006-07-26 16:18 [Bug fortran/28494] New: Unclear run time error message schnetter at aei dot mpg dot de
  2006-07-26 16:22 ` [Bug fortran/28494] " pinskia at gcc dot gnu dot org
@ 2006-09-20  8:27 ` tobias dot burnus at physik dot fu-berlin dot de
  2006-11-10 22:38 ` burnus at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: tobias dot burnus at physik dot fu-berlin dot de @ 2006-09-20  8:27 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from tobias dot burnus at physik dot fu-berlin dot de  2006-09-20 08:27 -------
I looked what other are writing:
----------------
gfortran:
Fortran runtime error: Array reference out of bounds for array 'r', upper bound
of dimension 1 exceeded (in file 'array2.f90', at line 4)

NAG f95:
Subscript 1 of R (value 5) is out of range (1:4)

Intel Fortran Compiler ifort:
forrtl: severe (408): fort: (2): Subscript #1 of the array R has value 5 which
is greater than the upper bound of 4

Sun f95:
 ******  FORTRAN RUN-TIME SYSTEM  ******
Subscript out of range. Location:  line 4 column 5 of 'array2.f90'
Subscript number 1 has value 5 in array 'R'
----------------

Personal favourite would be:

Fortran runtime error: Array reference out of bounds. Subscript 1 of array 'r'
(value 5) exceeds upper bound of 4 (in file 'array2.f90', at line 4)"

The place to change would be trans-array.c. I looked at it, but I fail to
extract a asprintf-able number from the "tree"s index etc.


-- 

tobias dot burnus at physik dot fu-berlin dot de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tobias dot burnus at physik
                   |                            |dot fu-berlin dot de


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


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

* [Bug fortran/28494] Unclear run time error message
  2006-07-26 16:18 [Bug fortran/28494] New: Unclear run time error message schnetter at aei dot mpg dot de
  2006-07-26 16:22 ` [Bug fortran/28494] " pinskia at gcc dot gnu dot org
  2006-09-20  8:27 ` tobias dot burnus at physik dot fu-berlin dot de
@ 2006-11-10 22:38 ` burnus at gcc dot gnu dot org
  2007-02-01 14:19 ` fxcoudert at gcc dot gnu dot org
  2007-08-14 13:42 ` fxcoudert at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: burnus at gcc dot gnu dot org @ 2006-11-10 22:38 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from burnus at gcc dot gnu dot org  2006-11-10 22:38 -------
As FX wrote in an email, a more-detailed error message can not be given with
the current method: at present the error string is constructed at compile time
via asprintf, but then the extend of the array might not be known - and the
current value neither.
One needs therefore to replace the current code by something which calls the
library.


-- 


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


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

* [Bug fortran/28494] Unclear run time error message
  2006-07-26 16:18 [Bug fortran/28494] New: Unclear run time error message schnetter at aei dot mpg dot de
                   ` (2 preceding siblings ...)
  2006-11-10 22:38 ` burnus at gcc dot gnu dot org
@ 2007-02-01 14:19 ` fxcoudert at gcc dot gnu dot org
  2007-08-14 13:42 ` fxcoudert at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2007-02-01 14:19 UTC (permalink / raw)
  To: gcc-bugs



-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-02-01 14:18:47
               date|                            |


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


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

* [Bug fortran/28494] Unclear run time error message
  2006-07-26 16:18 [Bug fortran/28494] New: Unclear run time error message schnetter at aei dot mpg dot de
                   ` (3 preceding siblings ...)
  2007-02-01 14:19 ` fxcoudert at gcc dot gnu dot org
@ 2007-08-14 13:42 ` fxcoudert at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2007-08-14 13:42 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #4 from fxcoudert at gcc dot gnu dot org  2007-08-14 13:42 -------
(In reply to comment #3)
> One needs therefore to replace the current code by something which calls the
> library.

This was done, and the current error message was corrected.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |4.3.0


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


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

end of thread, other threads:[~2007-08-14 13:42 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-07-26 16:18 [Bug fortran/28494] New: Unclear run time error message schnetter at aei dot mpg dot de
2006-07-26 16:22 ` [Bug fortran/28494] " pinskia at gcc dot gnu dot org
2006-09-20  8:27 ` tobias dot burnus at physik dot fu-berlin dot de
2006-11-10 22:38 ` burnus at gcc dot gnu dot org
2007-02-01 14:19 ` fxcoudert at gcc dot gnu dot org
2007-08-14 13:42 ` fxcoudert at gcc dot gnu dot 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).