13ceb48bc1
When building with LLVM's integrated assembler, the build errors because
it does not implement -mfix-loongson2f-{jump,nop}:
arch/mips/loongson2ef/Platform:36: *** only binutils >= 2.20.2 have needed option -mfix-loongson2f-nop. Stop.
The error is a little misleading because binutils are not being used in
this case.
To clear this up, remove the as-option calls because binutils 2.23 is
the minimum supported version for building the kernel. At the same time,
remove the cc-option calls for the '-march=' flags, as GCC 5.1.0 is the
minimum supported version.
This change will not fix the LLVM build for CONFIG_CPU_LOONGSON2{E,F},
as it does not implement the loongson2{e,f} march arguments (nor r4600,
so it will error prior to this change) nor the assembler flags mentioned
above but it will make the errors more obvious.
Link: https://github.com/ClangBuiltLinux/linux/issues/1529
Reported-by: Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp>
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
47 lines
1.8 KiB
Plaintext
47 lines
1.8 KiB
Plaintext
#
|
|
# Loongson Processors' Support
|
|
#
|
|
|
|
cflags-$(CONFIG_CPU_LOONGSON2EF) += -Wa,--trap
|
|
cflags-$(CONFIG_CPU_LOONGSON2E) += -march=loongson2e
|
|
cflags-$(CONFIG_CPU_LOONGSON2F) += -march=loongson2f
|
|
#
|
|
# Some versions of binutils, not currently mainline as of 2019/02/04, support
|
|
# an -mfix-loongson3-llsc flag which emits a sync prior to each ll instruction
|
|
# to work around a CPU bug (see __SYNC_loongson3_war in asm/sync.h for a
|
|
# description).
|
|
#
|
|
# We disable this in order to prevent the assembler meddling with the
|
|
# instruction that labels refer to, ie. if we label an ll instruction:
|
|
#
|
|
# 1: ll v0, 0(a0)
|
|
#
|
|
# ...then with the assembler fix applied the label may actually point at a sync
|
|
# instruction inserted by the assembler, and if we were using the label in an
|
|
# exception table the table would no longer contain the address of the ll
|
|
# instruction.
|
|
#
|
|
# Avoid this by explicitly disabling that assembler behaviour. If upstream
|
|
# binutils does not merge support for the flag then we can revisit & remove
|
|
# this later - for now it ensures vendor toolchains don't cause problems.
|
|
#
|
|
cflags-$(CONFIG_CPU_LOONGSON2EF) += $(call as-option,-Wa$(comma)-mno-fix-loongson3-llsc,)
|
|
|
|
# Enable the workarounds for Loongson2f
|
|
ifdef CONFIG_CPU_LOONGSON2F_WORKAROUNDS
|
|
cflags-$(CONFIG_CPU_NOP_WORKAROUNDS) += -Wa,-mfix-loongson2f-nop
|
|
cflags-$(CONFIG_CPU_JUMP_WORKAROUNDS) += -Wa,-mfix-loongson2f-jump
|
|
endif
|
|
|
|
# Some -march= flags enable MMI instructions, and GCC complains about that
|
|
# support being enabled alongside -msoft-float. Thus explicitly disable MMI.
|
|
cflags-y += $(call cc-option,-mno-loongson-mmi)
|
|
|
|
#
|
|
# Loongson Machines' Support
|
|
#
|
|
|
|
cflags-$(CONFIG_MACH_LOONGSON2EF) += -I$(srctree)/arch/mips/include/asm/mach-loongson2ef -mno-branch-likely
|
|
load-$(CONFIG_LEMOTE_FULOONG2E) += 0xffffffff80100000
|
|
load-$(CONFIG_LEMOTE_MACH2F) += 0xffffffff80200000
|