|When to do inline expansion jhall@whale.WPI.EDU (1993-09-14)|
|Re: When to do inline expansion email@example.com (1993-09-20)|
|Re: When to do inline expansion firstname.lastname@example.org (1993-09-20)|
|Re: When to do inline expansion email@example.com (1993-09-20)|
|Re: When to do inline expansion firstname.lastname@example.org (1993-09-21)|
|Re: When to do inline expansion email@example.com (1993-09-21)|
|Re: When to do inline expansion firstname.lastname@example.org (1993-09-21)|
|[7 later articles]|
|From:||jhall@whale.WPI.EDU (John Clinton Hall)|
|Organization:||Worcester Polytechnic Institute|
|Date:||Tue, 14 Sep 1993 17:34:39 GMT|
How long should a function be (in number of statements) for it to be a
reasonable speed optimization to perform inline expansion? (For
simplicity, let's assume that the function is only called once
throughout the code, and the source language is C.) Obviously, a
function with 100 statements should not be expanded; however, a
function with only 1 statement should be expanded inline.
My guess is that executing 3 to 5 statements would equal the time it
would normally take to set up the call, perform the call, and clean up
after the call. Comments?
Return to the
Search the comp.compilers archives again.