Re: [PHP4BETA] compile error

"Michael S. Steuer" <michael@steuer.com> writes: > |> That's what I was afraid for it meant... :( How come that PHP runs slower > |> like this... what does --disable-inline actually do to the binary? > |> > |> Thanks, > |> > |> Michael. > | > |Someone correct me if I'm wrong, but --disable-inline tells the compiler > |not to use inline functions but rather to make them regular functions. > |Inline functions have their code inserted into the calling function to > |eliminate the extra instruction(s) to call that function, thus speeding > |up the binary. > |-- > > This would also mean that inline-functions would result a much bigger > binary, because a lot of code would be duped in the process... everytime a > function gets called it is inserted into the calling function? I can see the > speed advantage (I think), but the earlier mentioned point is also true, > right? Or am I totally missing the point ? Well, not ALL functions, but only those specified as inline. And yes, it will increase the size of the binary. For this very reason inlining should usually only be used for small (or tiny even :) functions thats gets called a lot (preferable from not too many places to avoid too much duplication). Generally it doesn't make a HUGE impact on the binary size. though -- [ Below is a random fortune, which is unrelated to the above message. ] It's not reality that's important, but how you perceive things.