This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/30528] INTEGER(2) overflow
- From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Jan 2007 20:14:55 -0000
- Subject: [Bug fortran/30528] INTEGER(2) overflow
- References: <bug-30528-13962@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-01-21 20:14 -------
First, it should be noted that it's not legal code. Indeed, you might (or not)
be surprised by the behaviour of the code in question:
pito /tmp $ cat a.f
INTEGER*2 IWD1
IWD1 = 32768
PRINT *, IWD1
END
pito /tmp $ g77 a.f && ./a.out
-32768
This check is new in gfortran, the behaviour is intentional but can be
specificaly disabled using -fno-range-check:
$ gfortran -fno-range-check a.f && ./a.out
-32768
Closing bug report as INVALID. Making note to document this in the release
notes.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
GCC build triplet|powerpc-apple-darwin8 |
GCC host triplet|powerpc-apple-darwin8 |
GCC target triplet|powerpc-apple-darwin8 |
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30528