mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-11 12:28:41 +08:00
052c805a18
Commitccbef1674a("Kbuild, lto: add ld-version and ld-ifversion macros") introduced scripts/ld-version.sh for GCC LTO. At that time, this script handled 5 version fields because GCC LTO needed the downstream binutils. (https://lkml.org/lkml/2014/4/8/272) The code snippet from the submitted patch was as follows: # We need HJ Lu's Linux binutils because mainline binutils does not # support mixing assembler and LTO code in the same ld -r object. # XXX check if the gcc plugin ld is the expected one too # XXX some Fedora binutils should also support it. How to check for that? ifeq ($(call ld-ifversion,-ge,22710001,y),y) ... However, GCC LTO was not merged into the mainline after all. (https://lkml.org/lkml/2014/4/8/272) So, the 4th and 5th fields were never used, and finally removed by commit0d61ed17dd("ld-version: Drop the 4th and 5th version components"). Since then, the last 4-digits returned by this script is always zeros. Remove the meaningless last 4-digits. This makes the version format consistent with GCC_VERSION, CLANG_VERSION, LLD_VERSION. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Acked-by: Will Deacon <will@kernel.org> Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
60 lines
2.3 KiB
Plaintext
60 lines
2.3 KiB
Plaintext
#
|
|
# Loongson Processors' Support
|
|
#
|
|
|
|
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += -Wa,--trap
|
|
|
|
#
|
|
# 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_LOONGSON64) += $(call as-option,-Wa$(comma)-mno-fix-loongson3-llsc,)
|
|
|
|
#
|
|
# binutils from v2.25 on and gcc starting from v4.9.0 treat -march=loongson3a
|
|
# as MIPS64 R2; older versions as just R1. This leaves the possibility open
|
|
# that GCC might generate R2 code for -march=loongson3a which then is rejected
|
|
# by GAS. The cc-option can't probe for this behaviour so -march=loongson3a
|
|
# can't easily be used safely within the kbuild framework.
|
|
#
|
|
ifeq ($(call cc-ifversion, -ge, 0409, y), y)
|
|
ifeq ($(call ld-ifversion, -ge, 22500, y), y)
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += \
|
|
$(call cc-option,-march=loongson3a -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64)
|
|
else
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += \
|
|
$(call cc-option,-march=mips64r2,-mips64r2 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64)
|
|
endif
|
|
else
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += \
|
|
$(call cc-option,-march=mips64r2,-mips64r2 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64)
|
|
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_LOONGSON64) += -I$(srctree)/arch/mips/include/asm/mach-loongson64 -mno-branch-likely
|
|
load-$(CONFIG_CPU_LOONGSON64) += 0xffffffff80200000
|