|
@@ -166,16 +166,6 @@ cflags-$(CONFIG_CPU_CAVIUM_OCTEON) += -Wa,-march=octeon
|
|
endif
|
|
endif
|
|
cflags-$(CONFIG_CAVIUM_CN63XXP1) += -Wa,-mfix-cn63xxp1
|
|
cflags-$(CONFIG_CAVIUM_CN63XXP1) += -Wa,-mfix-cn63xxp1
|
|
cflags-$(CONFIG_CPU_BMIPS) += -march=mips32 -Wa,-mips32 -Wa,--trap
|
|
cflags-$(CONFIG_CPU_BMIPS) += -march=mips32 -Wa,-mips32 -Wa,--trap
|
|
-#
|
|
|
|
-# binutils from v2.25 on and gcc starting from v4.9.0 treat -march=loongson3a
|
|
|
|
-# as MIPS64 R1; 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.
|
|
|
|
-#
|
|
|
|
-cflags-$(CONFIG_CPU_LOONGSON3) += \
|
|
|
|
- $(call cc-option,-march=mips64r2,-mips64r2 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64) \
|
|
|
|
- -Wa,-mips64r2 -Wa,--trap
|
|
|
|
|
|
|
|
cflags-$(CONFIG_CPU_R4000_WORKAROUNDS) += $(call cc-option,-mfix-r4000,)
|
|
cflags-$(CONFIG_CPU_R4000_WORKAROUNDS) += $(call cc-option,-mfix-r4000,)
|
|
cflags-$(CONFIG_CPU_R4400_WORKAROUNDS) += $(call cc-option,-mfix-r4400,)
|
|
cflags-$(CONFIG_CPU_R4400_WORKAROUNDS) += $(call cc-option,-mfix-r4400,)
|