linux-kernel - [PATCH] Stop making "inline" imply forced inlining.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0701191156000.24621@CPE00045a9c397f-CM001225dbafb6>
Date:	Fri, 19 Jan 2007 11:56:30 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
cc:	rth@...ddle.net
Subject: [PATCH] Stop making "inline" imply forced inlining.

  Remove the macros that define simple "inlining" to mean forced
inlining, since you can (and *should*) get that effect with the
CONFIG_FORCED_INLINING kernel config variable instead.

Signed-off-by: Robert P. J. Day <rpjday@...dspring.com>

---

  this change was compile tested on x86 with "make allyesconfig",
followed by turning off forced inlining.

  now the alpha folks can simplify their compiler.h file. :-)

diff --git a/include/linux/compiler-gcc.h b/include/linux/compiler-gcc.h
index 6e1c44a..5a90bd9 100644
--- a/include/linux/compiler-gcc.h
+++ b/include/linux/compiler-gcc.h
@@ -23,9 +23,6 @@
     (typeof(ptr)) (__ptr + (off)); })

-#define inline		inline		__attribute__((always_inline))
-#define __inline__	__inline__	__attribute__((always_inline))
-#define __inline	__inline	__attribute__((always_inline))
 #define __deprecated			__attribute__((deprecated))
 #define  noinline			__attribute__((noinline))
 #define __attribute_pure__		__attribute__((pure))
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/