This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [gfortran,patch] Improve error messages for bounds-checking and a few other cases
- From: "François-Xavier Coudert" <fxcoudert at gmail dot com>
- To: "Tobias Burnus" <burnus at net-b dot de>
- Cc: fortran at gcc dot gnu dot org
- Date: Wed, 7 Jun 2006 10:55:21 +0200
- Subject: Re: [gfortran,patch] Improve error messages for bounds-checking and a few other cases
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ASfEB6CqmId75piX7pgIXSzfS4/L9Lcy/lmsLfD4U5rx6LEMOS/Blz7Nn/yshk4dwdKr5Xwm0fVfU+jnTDeQymQGM/20dcSpFf2qSqirPtONsO34/NYBpT0oZarW7hLyblBOENZhh8jp3Mzt07L4H03aeS8kLuS9rAhr46GDbsg=
- References: <31A70158-7AE3-4C92-9F70-4C54B9767541@gmail.com> <448690E0.9040008@net-b.de>
Could you also state which exect index was used (and maybe the
maximal/minimal allowed index)? In some more complicated programs it
helps to find the error. This is what other compilers are doing:
NAG: Subscript 2 of X (value 2) is out of range (1:1)
Ifort: Subscript #2 of the array X has value 2 which is greater than the
upper bound of 1
I'm thinking about doing that, yes. In fact, I almost settled down on
a way to implement that feature, but it has low priority and will do
it once I have fixed the last bugs remaining with -fbounds-check.
FX