[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-11-01 Thread fwi at inducks dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #11 from fwi at inducks dot org 2011-11-01 12:00:54 UTC --- (In reply to comment #10) > Sometimes abstractions leak, unfortunately. There's really not anything > gfortran can do about that. And, it's not unique to gfortran either. gfort

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-11-01 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #10 from Janne Blomqvist 2011-11-01 07:55:06 UTC --- (In reply to comment #8) > I indeed do not know everything about the OS and what it does when I > "allocate" > an array. But that's exactly the purpose of a programming language li

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread sgk at troutmask dot apl.washington.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #9 from Steve Kargl 2011-10-31 21:02:52 UTC --- On Mon, Oct 31, 2011 at 08:17:51PM +, fwi at inducks dot org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 > > --- Comment #8 from fwi at inducks dot org 2011-10-31 20:

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread fwi at inducks dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #8 from fwi at inducks dot org 2011-10-31 20:17:51 UTC --- I do not(In reply to comment #7) > On Mon, Oct 31, 2011 at 07:25:38PM +, fwi at inducks dot org wrote: > Yes, the problem of integer overflow that Janne mentioned has > been

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread sgk at troutmask dot apl.washington.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #7 from Steve Kargl 2011-10-31 19:50:41 UTC --- On Mon, Oct 31, 2011 at 07:25:38PM +, fwi at inducks dot org wrote: > > Has the bug been corrected in recent versions of gfortran, or do you really > mean it's OK that gfortran clai

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread fwi at inducks dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #6 from fwi at inducks dot org 2011-10-31 19:25:38 UTC --- Has the bug been corrected in recent versions of gfortran, or do you really mean it's OK that gfortran claims an array has been allocated when it really has not been?

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread fwi at inducks dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #4 from fwi at inducks dot org 2011-10-31 18:29:27 UTC --- I'm using: $ gfortran --version GNU Fortran (Ubuntu 4.4.3-4ubuntu5) 4.4.3 I've now tested the same program on a 64-bit CentOs machine with 16-Gb RAM, but

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #3 from Janne Blomqvist 2011-10-31 18:24:14 UTC --- >From the metadata, it seems you're using version 4.4.3, where the overflow check when calculating the size to allocate was a bit stupid. Basically it did the calculation, and if the

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread fwi at inducks dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 --- Comment #2 from fwi at inducks dot org 2011-10-31 18:15:57 UTC --- With "E=1.0D0" instead of "E(N,N,N,N)=1.0D0" $ gfortran test.f90; for i in `seq -w 10 10 400`; do LANG=C ./a.out $i; done Sucesfully allocated array of size 10 **4

[Bug fortran/50937] STAT option with ALLOCATE statement on large arrays

2011-10-31 Thread kargl at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org --- Co