This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [patch, fortran] PR36515 Integer read value overflow for a invalid integer.
- From: Tobias Burnus <burnus at net-b dot de>
- To: Jerry DeLisle <jvdelisle at verizon dot net>
- Cc: Fortran List <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 14 Jun 2008 20:50:56 +0200
- Subject: Re: [patch, fortran] PR36515 Integer read value overflow for a invalid integer.
- References: <48535D30.4080702@verizon.net>
Jerry DeLisle wrote:
To provide legacy compatibility with g77, this patch enables
-fno-range-check at runtime. This is done by adding the range-check
flag to the compile options array generated in trans-decl.c. The flag
is then used in read.c to ignore the overflow.
OK. However, can you document in invoke.texi which command-line options
affect the run-time behaviour of gfortran? I know of -std=,
-frange-check and -fsign-zero. I think there should be a note below each
of the options and maybe also a general note in the "Options for code
generation conventions" section.
Tobias