Arjan van de Ven wrote:
> gcc can and does optimize static functions more. A function being static > >(and not having it's address taken) means that gcc is aware of all >callers of this one function (unlike non-static obviously where places >outside the current .c may call it). That knowledge can and is used for >optimization. (and increasingly so in newer gcc's) > > > > > Interesting. We should use static wherever we can then.
