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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
