From: Arnd Bergmann <arnd@arndb.de>
To: Russell King <linux@armlinux.org.uk>
Cc: Nicolas Pitre <nico@linaro.org>, Andi Kleen <ak@linux.intel.com>,
Richard Earnshaw <rearnsha@gcc.gnu.org>,
Tamar Christina <tnfchris@gcc.gnu.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] ARM: xscale: fix gcc-8 build
Date: Fri, 2 Feb 2018 16:07:35 +0100 [thread overview]
Message-ID: <20180202150756.420422-2-arnd@arndb.de> (raw)
In-Reply-To: <20180202150756.420422-1-arnd@arndb.de>
We use a hack in xscale-cp0.c to allow building it for ARMv4 while
also using ARMv5TE and iWMMXt specific inline assembly, by
adding a top-level asm statement.
Unfortunately that hack no longer works with gcc-8, since it will
revert back to the normal architecture. The recommended way of
handling this is to use __attribute__((target("armv5te"))) on the
functions that need it, or #pragma GCC target("arch=armv5te").
Either of those work with gcc-8, but not earlier versions, and
it seems worse to combine that with the old hack.
Instead, this adds the .arch statement to each inline assembler
statement that needs it individually. That is also slightly uglier
than the previous hack, but it works with all compiler versions
and documents better why we need the override in the first place.
Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84129
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
arch/arm/kernel/xscale-cp0.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/arch/arm/kernel/xscale-cp0.c b/arch/arm/kernel/xscale-cp0.c
index 77a2eef72115..e06a2f6dac4f 100644
--- a/arch/arm/kernel/xscale-cp0.c
+++ b/arch/arm/kernel/xscale-cp0.c
@@ -17,11 +17,10 @@
#include <asm/thread_notify.h>
#include <asm/cputype.h>
-asm(" .arch armv5te\n");
-
static inline void dsp_save_state(u32 *state)
{
__asm__ __volatile__ (
+ ".arch armv5te\n\t"
"mrrc p0, 0, %0, %1, c0\n"
: "=r" (state[0]), "=r" (state[1]));
}
@@ -29,6 +28,7 @@ static inline void dsp_save_state(u32 *state)
static inline void dsp_load_state(u32 *state)
{
__asm__ __volatile__ (
+ ".arch armv5te\n\t"
"mcrr p0, 0, %0, %1, c0\n"
: : "r" (state[0]), "r" (state[1]));
}
@@ -134,7 +134,8 @@ static int __init cpu_has_iwmmxt(void)
* tmrrc %0, %1, wR0
*/
__asm__ __volatile__ (
- "mcrr p0, 0, %2, %3, c0\n"
+ ".arch armv5te\n\t"
+ "mcrr p0, 0, %2, %3, c0\n\t"
"mrrc p0, 0, %0, %1, c0\n"
: "=r" (lo), "=r" (hi)
: "r" (0), "r" (0x100));
--
2.9.0
next prev parent reply other threads:[~2018-02-02 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 15:07 [PATCH 1/2] ARM: kvm: fix building with gcc-8 Arnd Bergmann
2018-02-02 15:07 ` Arnd Bergmann [this message]
2018-02-02 16:39 ` [PATCH 2/2] ARM: xscale: fix gcc-8 build Nicolas Pitre
2018-02-02 15:55 ` [PATCH 1/2] ARM: kvm: fix building with gcc-8 Robin Murphy
2018-02-02 16:23 ` Robin Murphy
2018-02-02 16:29 ` Arnd Bergmann
2018-02-02 16:30 ` Robin Murphy
2018-02-04 18:45 ` Christoffer Dall
2018-02-04 20:57 ` Arnd Bergmann
2018-02-05 8:33 ` Christoffer Dall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180202150756.420422-2-arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ak@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nico@linaro.org \
--cc=rearnsha@gcc.gnu.org \
--cc=tnfchris@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®