Re: the Evil Effects of Inlining

Ooops. I wrote something very unclear:


>Preston Briggs writes:
>>[Register allocators aren't as smart as bind save/restore at
>> the call site.]


pardo@june.cs.washington.edu (David Keppel) writes:
>[Technique...] 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.).


Gee, it sounds like I'm saying that a function call is the worst of all
possible worlds, when I was talking about avoiding the function call.
What I *meant* to say (I really did re-read it, but it made sense at
the time) was that if you:


* Do register saves and restores in the caller like you were doing a
    function call
* Do register allocation in the callee like it was a real function
* Inline the function


then you can:


* Use the same register allocation strategy and get no worse register
    allocation
* Remove redundant register saves and restores
* Remove redundant branches


Hopefully it make sense this time.


;-D on ( Confusion reigns supreme ) Pardo
--

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