summaryrefslogtreecommitdiff
path: root/Rules.mak
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2016-03-20 17:58:35 +0100
committerWaldemar Brodkorb <wbx@openadk.org>2016-03-31 19:35:13 +0200
commitfeb9f08cfe8ddd1fd4fb62265e17ee35147ab268 (patch)
treeda452e5e8aa09cd6ef0c9d9d83033a8d4f3d623c /Rules.mak
parent4ab024d22980cf493dc95a089353df6ebc743f46 (diff)
arm: simplify handling of Thumb related options
Currently, the Thumb support on ARM has three related Config.in options, which are not trivial for users to understand, and are in fact not needed: - The USE_BX option is not needed: knowing whether BX is available or not is easy. If you have an ARM > v4 or ARMv4T, then BX is available, otherwise it's not. This is the logic used in glibc. - The USE_LDREXSTREX option is not needed: whenever Thumb2 is available, ldrex/strex are available, so we can simply rely on __thumb2__ to determine whether ldrex/strex should be used, without requiring a Config.in option. - Once USE_BX and USE_LDREXSTREX are removed, the only thing left that COMPILE_IN_THUMB does is to set -mthumb. This makes the option unnecessary, as on ARM at least, the user is already supposed to pass -march=<foo> or other compiler options tuning the library for a specific ARM variant. There is no reason to do otherwise for Thumb, which allows to get rid of the COMPILE_IN_THUMB option. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'Rules.mak')
-rw-r--r--Rules.mak1
1 files changed, 0 insertions, 1 deletions
diff --git a/Rules.mak b/Rules.mak
index fc53ad13a..dc1a02e51 100644
--- a/Rules.mak
+++ b/Rules.mak
@@ -392,7 +392,6 @@ endif
ifeq ($(TARGET_ARCH),arm)
CPU_CFLAGS-$(ARCH_LITTLE_ENDIAN)+=-mlittle-endian
CPU_CFLAGS-$(ARCH_BIG_ENDIAN)+=-mbig-endian
- CPU_CFLAGS-$(COMPILE_IN_THUMB_MODE)+=-mthumb
endif
ifeq ($(TARGET_ARCH),metag)