Re: Status of CONFIG_FORCED_INLINING?

Arjan van de Ven
2007-05-23T21:33:00Z

Adrian Bunk wrote:
>
> What about performance reasons?
> We habe "inline" code in header files that heavily relies on being
> nearly completely optimized away after being inlined.

fair

> Especially with -Os it could even sound logical for a compiler to never
> inline a non-forced "inline"'d three line function with 2 callers.

but you said "I Care about size more than performance". Your argument
is thus absolutely incorrect.

> The rules are simple:
> - every static function in a header file must be __always_inline

wrong.

>
> Your suggestion is possible, but please also send a patch that turns
> every "inline" in header files into __always_inline...

this is 1) insane and 2) if inlines in headers are so big gcc decides
to not inline them.. they're too big and don't belong in the header.