[RFC][PATCH] Fix inlining size in gcc3

• Next message: Bryan O'Sullivan: "Re: [2.5.72] Oops on x86_64 running 32-bit code"
• Previous message: Steve French: "duplicate entry check in kmem_cache_create"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi.

This is one other patch collected from the list. It fixes cases when gcc3
can choose to inline or not inline some functions based on its size, even
if are declared inline.

Credtis go to Andrew Morton <akpm@digeo.com>

--- 25/include/linux/compiler.h~gcc3-inline-fix 2003-03-06 03:02:43.000000000 -0800
+++ 25-akpm/include/linux/compiler.h 2003-03-06 03:11:42.000000000 -0800
@@ -1,6 +1,13 @@
 #ifndef __LINUX_COMPILER_H
 #define __LINUX_COMPILER_H
 
+#if __GNUC__ >= 3
+#define inline __inline__ __attribute__((always_inline))
+#define inline__ __inline__ __attribute__((always_inline))
+#define __inline __inline__ __attribute__((always_inline))
+#define __inline__ __inline__ __attribute__((always_inline))
+#endif
+
 /* Somewhere in the middle of the GCC 2.96 development cycle, we implemented
    a mechanism by which the user can annotate likely branch directions and
    expect the blocks to be reordered appropriately. Define __builtin_expect

-- 
J.A. Magallon <jamagallon@able.es>      \                 Software is like sex:
werewolf.able.es                         \           It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.21-jam1 (gcc 3.3 (Mandrake Linux 9.2 3.3-1mdk))
-
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/

• Next message: Bryan O'Sullivan: "Re: [2.5.72] Oops on x86_64 running 32-bit code"
• Previous message: Steve French: "duplicate entry check in kmem_cache_create"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Jun 23 2003 - 22:00:27 EST