From: James Morris <jmorris@intercode.com.au>
Date: Thu, 15 May 2003 15:38:15 +1000 (EST)
I wonder, does this mean that the compiler failed to inline the function?
Removing __inline__ is not the correct solution.
I already posted what the correct fix is :-) And this is already
pushed to 2.5.x
Inlining is not guarenteed, and:
extern inline ... foo(...)
means "inline if you can, I have a compiled-in implementation
in some object somewhere" whereas:
static inline ... foo(...)
means "inline if you can, if there is a case where you cannot
emit this as a function into the current module"
-
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/
This archive was generated by hypermail 2b29 : Thu May 15 2003 - 22:00:55 EST