[<prev] [next>] [day] [month] [year] [list]
Message-Id: <691ab4fcf6b6b69d1db91b94d404cb80fca36f6c.1633523760.git.geert+renesas@glider.be>
Date: Wed, 6 Oct 2021 14:40:22 +0200
From: Geert Uytterhoeven <geert+renesas@...der.be>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: linux-kernel@...r.kernel.org,
Geert Uytterhoeven <geert+renesas@...der.be>
Subject: [PATCH] compiler-intel: Remove duplicate RELOC_HIDE()
The RELOC_HIDE() implementation for the Intel compiler is identical to
the generic version in <linux/compiler.h>, so the former can just be
removed.
Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
---
Not even compile-tested.
---
include/linux/compiler-intel.h | 5 -----
1 file changed, 5 deletions(-)
diff --git a/include/linux/compiler-intel.h b/include/linux/compiler-intel.h
index b17f3cd18334df3d..efc8fafb58f595b2 100644
--- a/include/linux/compiler-intel.h
+++ b/include/linux/compiler-intel.h
@@ -16,11 +16,6 @@
#define barrier() __memory_barrier()
#define barrier_data(ptr) barrier()
-#define RELOC_HIDE(ptr, off) \
- ({ unsigned long __ptr; \
- __ptr = (unsigned long) (ptr); \
- (typeof(ptr)) (__ptr + (off)); })
-
/* This should act as an optimization barrier on var.
* Given that this compiler does not have inline assembly, a compiler barrier
* is the best we can do.
--
2.25.1
Powered by blists - more mailing lists