> Richard Guenther writes: > ... I also think our in-lining limits are way too high, > at least unnecessary high with the patch applied...
- If function-call overhead could be more accurately estimated, possibly by enabling the inclusion of set/move instructions in rtl cost estimates to more accurately account for a function's variable and/or constant parameter call overhead based on the target's machine description, then the in-lining limit may be more productively expressed as a ratio ranging from 0 to 2-3x code-growth limit based on the estimated in-lined-code/call-overhead based on optimization goals; thereby enabling in-lining limits to be expressed similarly to loop-unrolling limit's, as it's this ratio which would seem to most likely estimates it's benefit?
