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/80610] Compiler crashes ungraciously when large static array is initialized with anything other than zero


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80610

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from kargl at gcc dot gnu.org ---
(In reply to Gustavo Hime from comment #3)
> I (In reply to kargl from comment #2)
> > The reported error message "virtual memory exhausted: Cannot allocate memory"
> > is fairly descriptive.  Allocating a 1 GB static array is a rather silly
> > thing for a programmer to do.
> 
> Please mind your tone. And refrain from arbitrarily closing a bug just
> because you cannot understand the gravity of it.

I understand the issue.  It isn't a problem with gfortran.

> A compiler that crashes, no matter how preposterous the source code that led
> it to crash, is trash. Any software that crashes ungraciously is trash.
> Either work for improving the GCC suite or keep quiet.

The compiler did not crash.  Your operating system terminated your
process because you exhausted the virtual memory available to you.
The error message even tells you what you have done.

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