This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/32124] New: Execution stops with stat= in ALLOCATE
- From: "sfilippone at uniroma2 dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 May 2007 09:35:08 -0000
- Subject: [Bug fortran/32124] New: Execution stops with stat= in ALLOCATE
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
The attached program never reaches the error message printout, contrary to the
fact that stat= is specified in the allocate statement (if the runtime aborts,
what's the point of stat= ?)
[sfilippo@localhost bugtest]$ gfortran -o tryalloc tryalloc.f90
[sfilippo@localhost bugtest]$ ./tryalloc
Fortran runtime error: Attempt to allocate negative amount of memory. Possible
integer overflow
[sfilippo@localhost bugtest]$ gfortran -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.2.0/configure --prefix=/usr/local/gcc42
--with-mpfr=/home/travel/GCC/BUILDS/mpfr
--with-gmp-lib=/home/travel/GCC/BUILDS/gmp/lib/
--with-gmp=/home/travel/GCC/BUILDS/gmp
Thread model: posix
gcc version 4.2.0
--
Summary: Execution stops with stat= in ALLOCATE
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: sfilippone at uniroma2 dot it
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32124