summaryrefslogtreecommitdiffstats
path: root/arch/mips/pmcs-msp71xx
diff options
context:
space:
mode:
authorMaciej W. Rozycki <macro@linux-mips.org>2014-06-29 01:59:35 +0200
committerRalf Baechle <ralf@linux-mips.org>2014-07-30 15:53:49 +0200
commitb625cd4aa417b979e59359a8ca020cad8e032df1 (patch)
treebe431c89eb786dde7abf932d9a24367bd3d21467 /arch/mips/pmcs-msp71xx
parentMIPS: asm/bitops.h: Guard CLZ with `.set mips32' (diff)
downloadlinux-b625cd4aa417b979e59359a8ca020cad8e032df1.tar.xz
linux-b625cd4aa417b979e59359a8ca020cad8e032df1.zip
MIPS: SB1: Check optional compilation flags one by one
This fixes a regression caused by commit bb6c0bd3fdb67c8a1fceea1d4700b9ee593309f9 [MIPS: SB1: Fix excessive kernel warnings.], that makes `-march=r5000' selected for compilation flags rather than supposed `-march=sb1' with compilers that do not support the ASE selection flags introduced with that change. For example GCC 4.1.2 supports `-mips3d'/`-mno-mips3d' (and obviously `-march=sb1'), however it does not support `-mdmx'/`-mno-mdmx'. As a result the whole selection of flags fails and compilation resorts to using `-march=r5000', meant for really old compilers indeed only. It is always best to pick the flags individually unless we are absolutely sure a set of flags was introduced to the toolchain together (`-march=sb1' and `-mtune=sb1' would be a good example), and this change makes it happen for CONFIG_CPU_SB1. Consequently the flags ultimately selected with GCC 4.1.2 are `-march=sb1 -Wa,--trap -mno-mips3d' Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org> Cc: Richard Sandiford <rdsandiford@googlemail.com> Cc: linux-mips@linux-mips.org Patchwork: https://patchwork.linux-mips.org/patch/7223/ Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Diffstat (limited to 'arch/mips/pmcs-msp71xx')
0 files changed, 0 insertions, 0 deletions