Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact

Andi Kleen
2009-01-10T00:23:19Z

> What's the cost/benefit of that 4%? Does it actually improve performance?
> Especially if you then want to keep DWARF unwind information in memory in
> order to fix up some of the problems it causes? At that point, you lost

dwarf unwind information has nothing to do with this, it doesn't tell
you anything about inlining or not inlining. It just gives you
finished frames after all of that has been done.

Full line number information would help, but I don't think anyone
proposed to keep that in memory.

> Does it help I$ utilization (which can speed things up a lot more, and is
> probably the main reason -Os actually tends to perform better)? Likely
> not. Sure, shrinking code is good for I$, but on the other hand inlining
> can actually be bad for I$ density because if you inline a function that
> doesn't get called, you now fragmented your footprint a lot more.

Not sure that is always true; the gcc basic block reordering
based on its standard branch prediction heuristics (e.g. < 0 or
== NULL unlikely or the unlikely macro) might well put it all out of line.

-Andi