https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80318
benjamin.redelings at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Version|7.0.1 |8.1.0 --- Comment #4 from benjamin.redelings at gmail dot com --- It seems like the time and RAM usage for me is: -g: 5.3g / ~100s -g -fno-var-tracking -fno-var-tracking-assignments: 4.6g / ~80s no -g: 2.3g / 43s So, while it is true that var-tracking is a problem, it is clearly not the whole problem. Also for clang we have: clang -g: 2.2g / 93s clang no -g: 1.2g / 42s So clang is not suffering from the RAM hogging problems, at least. Any suggestions for a path forward on identifying (say) the second-largest memory hog, after var-tracking?