https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81818
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Looking for memory leaks in the backend might be interesting. Note you can build GCC with --enable-gather-detailed-mem-stats and use -fmem-report to get an idea where memory is allocated (and freed).