On 11/7/19 2:34 PM, Jozef Lawrynowicz wrote: > 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. > I'm not a huge fan of making the default configurations behave differently. But I can also see how something like TM in particular isn't of much interest in the embedded space (hell, it's having trouble getting real traction in the server space as well).
May be a reasonable path forward is to add the configury bits, keep TM on by default and create a different msp target which disables this stuff? Jeff ps. I thought libitm would fallback to a full software solution and the hardware requirements were really just enabling fast-paths.
