Re: Inlining doesn't happen on OS X: big performance problem

["Óscar Fuentes" <ofv@wanadoo.es>]

Daniel Colascione <dancol@dancol.org> writes:

>>>> Why doesn't the compiler inline static functions by itself?
>>>
>>> Why should it?
>> 
>> There is no reason not to do it.
>
> Sure there is: programs would be huge if compilers naively treated every
> "static" as "inline, so they don't. Instead, compilers inline some
> static functions, some of the time, and the heuristics they use for
> deciding whether to do that are inscrutable and variable. Why should we
> rely on these heuristics for good performance when we just write "static
> inline" and make the decision ourselves?

The days when the programmer knew better than the compiler about
micro-optimization are long gone, even more so on cross-platform code.

[snip]

>>> Why should we remove this hint?
>> 
>> "Hint" is the essential hint.
>
> What's wrong with leaving hints in the code? We still have "register"
> all over the place, and "static inline" does much more than "register".

Nowadays "register" is as meaningless as "inline".