[Bug fortran/41102] Ease error checking of included files located in the SYSTEM_INCLUDE_DIR/ending in .h

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41102 fwi at inducks dot org changed: What|Removed |Added CC||fwi at inducks dot org

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

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

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

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 +0000, fwi at inducks dot org wrote: > Yes, the problem of integer overflow that Janne mention

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

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

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-G

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

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 s

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937 Bug #: 50937 Summary: STAT option with ALLOCATE statement on large arrays Classification: Unclassified Product: gcc Version: 4.4.3 Status: UNCONFIRMED Severity: minor

[Bug fortran/50924] Attempt to allocate negative amount of memory. Possible integer overflow

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50924 --- Comment #4 from fwi at inducks dot org 2011-10-31 08:43:23 UTC --- Actually contrary to what I wrote my system is 64 bit (I clicked on "edit" on the top right and somehow the system sent a message that I was starting to write). St

[Bug fortran/50924] Attempt to allocate negative amount of memory. Possible integer overflow

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50924 fwi at inducks dot org changed: What|Removed |Added CC||fwi at inducks dot org

[Bug fortran/50924] New: Attempt to allocate negative amount of memory. Possible integer overflow

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50924 Bug #: 50924 Summary: Attempt to allocate negative amount of memory. Possible integer overflow Classification: Unclassified Product: gcc Version: 4.4.3 Status: UNCONF