Jan Hubicka <hubicka@ucw.cz> writes:
I am not sure why ggc_alloc comes in second; checking is disabled so
My experience from oprofiling is, that ggc_alloc/garbage
collector/memset is where all our cache faults go, so they end up
high in profiles even when amount of work looks small. It is not
really ggc_alloc fault, rather it is the fact that we use too much
of it.
True.
One cause of excessive memset that I have wanted to address for years
is, make_node() clears the entire tree node - but make_node is almost
always called from somewhere that's going to fill in most or all of
the fields anyway. We ought to have something like the gen_rtx_fmt_*
functions for tree nodes.