Messages in this thread | | | Date | Thu, 23 Sep 2004 09:50:26 -0700 | From | William Lee Irwin III <> | Subject | Re: __attribute__((always_inline)) fiasco |
| |
On Thu, Sep 23, 2004 at 12:26:18PM -0400, Albert Cahalan wrote: > #define INLINE > #define INLINE inline > #define INLINE static inline // an oxymoron > #define INLINE extern inline // an oxymoron > #define INLINE __force_inline > #define INLINE __attribute__((always_inline)) > #define INLINE _Pragma("inline") > #define INLINE __inline_or_die_you_foul_compiler > #define INLINE _Please inline
The // apart from being a C++ ism (screw C99; it's still non-idiomatic) will cause spurious ignorance of the remainder of the line, which is often very important. e.g.
static INLINE int lock_need_resched(spinlock_t *lock) { ...
-- wli - 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/
| |