summaryrefslogtreecommitdiffstats
path: root/arch/arc/kernel
diff options
context:
space:
mode:
authorVineet Gupta <vgupta@synopsys.com>2019-03-05 18:16:29 +0100
committerVineet Gupta <vgupta@synopsys.com>2019-03-05 18:16:33 +0100
commit6dd356d8fc0641a8f0afb6ba457fb9351eea5076 (patch)
treebf73566b623c1b95a60f50aced06071ac4ee05c2 /arch/arc/kernel
parentARC: boot log: cut down on verbosity (diff)
downloadlinux-6dd356d8fc0641a8f0afb6ba457fb9351eea5076.tar.xz
linux-6dd356d8fc0641a8f0afb6ba457fb9351eea5076.zip
ARC: unaligned: relax the check for gcc supporting -mno-unaligned-access
Without bleeding edge gcc, kernel builds were tripping everywhere. So current gcc will generate unaligned code despite !CONFIG_ARC_USE_UNALIGNED_MEM_ACCESS but that is something we have to live with. Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Diffstat (limited to 'arch/arc/kernel')
-rw-r--r--arch/arc/kernel/setup.c12
1 files changed, 0 insertions, 12 deletions
diff --git a/arch/arc/kernel/setup.c b/arch/arc/kernel/setup.c
index 15da43d2e416..a9c88b7e9182 100644
--- a/arch/arc/kernel/setup.c
+++ b/arch/arc/kernel/setup.c
@@ -314,18 +314,6 @@ static char *arc_cpu_mumbojumbo(int cpu_id, char *buf, int len)
IS_AVAIL1(cpu->extn_mpy.ver, mpy_opt),
IS_AVAIL1(cpu->isa.div_rem, "div_rem "));
-
-#if defined(__ARC_UNALIGNED__) && !defined(CONFIG_ARC_USE_UNALIGNED_MEM_ACCESS)
- /*
- * gcc 7.3.1 (GNU 2018.03) onwards generate unaligned access by default
- * but -mno-unaligned-access to disable that didn't work until gcc 8.2.1
- * (GNU 2019.03). So landing here implies the interim period, when
- * despite Kconfig being off, gcc is generating unaligned accesses which
- * could bomb later on. So better to disallow such broken builds
- */
- BUILD_BUG_ON_MSG(1, "gcc doesn't support -mno-unaligned-access");
-#endif
-
if (cpu->bpu.ver) {
n += scnprintf(buf + n, len - n,
"BPU\t\t: %s%s match, cache:%d, Predict Table:%d Return stk: %d",