Given that MSP430 is a resource constrained, embedded target disabling transactional memory by default is a good idea to save on code size in the runtime library.
It can still be enabled by passing --enable-tm-clone-registry (although as far as I understand the feature is fundamentally incompatible with MSP430 given reliance on libitm, lack of thread support without an OS and the memory limitations of the device.
>From 9dfc5fde568c5a4cd29471888bff538943a995b1 Mon Sep 17 00:00:00 2001 From: Jozef Lawrynowicz <joze...@mittosystems.com> Date: Tue, 29 Oct 2019 14:49:08 +0000 Subject: [PATCH 1/4] MSP430: Disable TM clone registry by default libgcc/ChangeLog: 2019-11-07 Jozef Lawrynowicz <joze...@mittosystems.com> * configure: Regenerate. * configure.ac (tm-clone-registry): Disable by default for MSP430. --- libgcc/configure | 9 +++++++++ libgcc/configure.ac | 8 ++++++++ 2 files changed, 17 insertions(+) diff --git a/libgcc/configure b/libgcc/configure index 117e9c97e57..26d4d68a510 100755 --- a/libgcc/configure +++ b/libgcc/configure @@ -4964,6 +4964,15 @@ if test "$enable_tm_clone_registry" = no; then use_tm_clone_registry=-DUSE_TM_CLONE_REGISTRY=0 fi +else + +use_tm_clone_registry= +case $target in + msp430*) + use_tm_clone_registry=-DUSE_TM_CLONE_REGISTRY=0 + ;; +esac + fi diff --git a/libgcc/configure.ac b/libgcc/configure.ac index f63c5e736e5..0f225b84117 100644 --- a/libgcc/configure.ac +++ b/libgcc/configure.ac @@ -268,6 +268,14 @@ use_tm_clone_registry= if test "$enable_tm_clone_registry" = no; then use_tm_clone_registry=-DUSE_TM_CLONE_REGISTRY=0 fi +], +[ +use_tm_clone_registry= +case $target in + msp430*) + use_tm_clone_registry=-DUSE_TM_CLONE_REGISTRY=0 + ;; +esac ]) AC_SUBST([use_tm_clone_registry]) -- 2.17.1
