summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDave Martin <Dave.Martin@arm.com>2019-06-06 11:33:43 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-06-25 11:34:52 +0800
commitae4e62064756dba432c3691360ba80bba7a1191e (patch)
tree54d468bc258a00a30e47e37154ca69d23e694c17
parent4cfd8b68135572f0ac45e2e12eaea07bbefe6155 (diff)
downloadlinux-stable-ae4e62064756dba432c3691360ba80bba7a1191e.tar.gz
linux-stable-ae4e62064756dba432c3691360ba80bba7a1191e.tar.bz2
linux-stable-ae4e62064756dba432c3691360ba80bba7a1191e.zip
arm64: Silence gcc warnings about arch ABI drift
[ Upstream commit ebcc5928c5d925b1c8d968d9c89cdb0d0186db17 ] Since GCC 9, the compiler warns about evolution of the platform-specific ABI, in particular relating for the marshaling of certain structures involving bitfields. The kernel is a standalone binary, and of course nobody would be so stupid as to expose structs containing bitfields as function arguments in ABI. (Passing a pointer to such a struct, however inadvisable, should be unaffected by this change. perf and various drivers rely on that.) So these warnings do more harm than good: turn them off. We may miss warnings about future ABI drift, but that's too bad. Future ABI breaks of this class will have to be debugged and fixed the traditional way unless the compiler evolves finer-grained diagnostics. Signed-off-by: Dave Martin <Dave.Martin@arm.com> Signed-off-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
-rw-r--r--arch/arm64/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
index b025304bde46..8fbd583b18e1 100644
--- a/arch/arm64/Makefile
+++ b/arch/arm64/Makefile
@@ -51,6 +51,7 @@ endif
KBUILD_CFLAGS += -mgeneral-regs-only $(lseinstr) $(brokengasinst)
KBUILD_CFLAGS += -fno-asynchronous-unwind-tables
+KBUILD_CFLAGS += -Wno-psabi
KBUILD_AFLAGS += $(lseinstr) $(brokengasinst)
KBUILD_CFLAGS += $(call cc-option,-mabi=lp64)