http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #6 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-11-13
11:59:48 UTC ---
(In reply to comment #4)
> Why is GCC comsuming so much memory?
>
> The program has 6.4MB source code, it is a single function. All optimizations
> are turned off. And there is 2GB memory in the system.
>
> Well, shouldn't it be possible to compile this program?
That depends on the program, where the memory goes, possible bugs, etc.
To start investigating this, GCC devs would need the info requested here:
http://gcc.gnu.org/bugs/#report
That said, even if you provided that info, it is unlikely that anyone will look
into this bug, since it is a unusual case. If adding 2 or 4 more GBs of memory
(or splitting the function into many small pieces) solves the issue, then it is
simpler to just do that, and focus on fixing other bugs.
Of course, nothing prevents you from investigating the issue yourself. Perhaps
you are able to uncover a clear bug, memory leak or potential improvement. See:
http://gcc.gnu.org/wiki/Speedup_areas
http://gcc.gnu.org/wiki/Memory_management
http://gcc.gnu.org/wiki/PerformanceTesting
