https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107060
--- Comment #10 from Paul Eggert <eggert at cs dot ucla.edu> --- Created attachment 58064 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58064&action=edit "gunzip u.i" then "gcc -O2 -S -fanalyzer u.i" to see how much memory GCC uses I'm having more trouble with this when using gcc (GCC) 14.0.1 20240411 (Red Hat 14.0.1-0) on x86-64. I am now getting "gcc: fatal error: Killed signal terminated program cc1" when compiling Emacs xdisp.c. To reproduce the problem, run gunzip u.i gcc -O2 -S -fanalyzer u.i with the attached file u.i.gz. GCC keeps allocating more and more virtual memory, almost all via brk (wouldn't mmap be better? but I digress) until it goes past 10 GB and exhausts my little machine's swap space (7.7G of zram). I didn't see this problem with GCC 13 on Fedora 39, so in some sense I suppose this is a regression. Maybe there's a new memory leak of some sort? Or perhaps it's just -fanalyzer doing new checks for GCC 14.