https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80610
Gustavo Hime <gustavo.hime at mpimet dot mpg.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #3 from Gustavo Hime <gustavo.hime at mpimet dot mpg.de> ---
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.
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.
I was lucky to have discovered the bug because of a typo. I wonder it had
triggered because of some constellation of preprocessed constants set inside a
perl build script combined with parameters scattered over several source files
in different directories - and then after years successfully building your
1000+ source file project suddenly somebody in the other side of the planet
changes one such number and your the code no longer compiles. That would indeed
be silly.
