Messages in this thread | | | Subject | Re: Status of CONFIG_FORCED_INLINING? | From | Roland Dreier <> | Date | Thu, 24 May 2007 10:14:41 -0700 |
| |
> A function only belongs into a header file if we always want it inlined, > otherwise it belongs into a C file.
Again, why? Why don't we trust the compiler to decide if a function should be inlined or not, even if the definition happens to be in a .h file?
It seems like a perfectly valid optimization for the compiler to only emit code once for a function and then call it where it is used, even if that function happens to be defined in a .h file.
- R. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |