https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109509
--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> --- For a summary - PR109491 does not seem to be about integration time. most time is RTL PRE. - PR108086 has 10% spent in integration and seems to be operand scan issue - PR99785 is hard to judge given that it is a large inline bomb. Clang compiles it faster but it compiles different code, because Firefox gfx library now has two vector iplementations. Clang is not able to copmile gcc path and gcc is not able to compile clang path. - PR79416 has large inline stack, so we eventually run out of memory. Looking at the profile, 15% is spent by ggc_internal_alloc, so it seems that tree-inline is actually doing its job, just has too much of it.
