https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> --- On July 9, 2018 5:18:40 PM GMT+02:00, "boris.staletic at gmail dot com" <gcc-bugzi...@gcc.gnu.org> wrote: >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422 > >--- Comment #10 from Boris Staletic <boris.staletic at gmail dot com> >--- >Running "g++ -S -fno-exceptions CodePoint.cpp" didn't run into OOM >killer, but >gcc still hanged. The memory usage at maximum was 15.6GB. What I find >strange >is that "htop" reported the g++ process as dead most of the time and >the CPU >usage was 20% to 25% (or less) while that was happening. That's to be expected when it runs into swap. GCC is bad at keeping the active memory set small because it uses garbage collection and the mark and sweep phase pages in everything...
