This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50937

Janne Blomqvist <jb at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |jb at gcc dot gnu.org
         Resolution|                            |INVALID

--- Comment #5 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-10-31 19:01:59 UTC ---
(In reply to comment #4)
>     I've now tested the same program on a 64-bit CentOs machine 
>     with 16-Gb RAM, but wasn't able to reproduce the problem there:

Yes, because on a 64-bit platform the size calculation is done with 64-bit
integers, and long before such integers overflow the OS decides to deny the
allocation request (as can be seen e.g. by the different error code).

I'm not really seeing any bug here.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]