Re: the Evil Effects of Inlining

>Preston Briggs writes:
>>[Some reasons why you might not want to inline]
> REGISTER PRESSURE:
> Call sites are natural places to spill lots of registers.
> Register allocators are rarely able to achieve the same efficiency.


daniel@quilty.Stanford.EDU (Daniel Weise) writes:
>[So we have to make better register allocators.]


Stronger than that: if the call site is the right place to save/restore
registers, then save and restore registers at the call site, around the
inlined function. Then delete any redundant (useless) saves and
restores.


On the basis of register pressure, you couldn't possibly do worse than
a function call. You might still suffer all the other side effects
(code growth, etc.).


;-D on ( It's all caching ) Pardo
--

Return to the comp.compilers page.
Search the comp.compilers archives again.