Re: [PATCH 1/4] MSP430: Disable TM clone registry by default

2019-11-24 Thread Jozef Lawrynowicz
On Sun, 24 Nov 2019 10:10:51 -0700 Jeff Law wrote: > On 11/24/19 7:20 AM, Jozef Lawrynowicz wrote: > > On Sun, 17 Nov 2019 12:11:23 -0700 > > Jeff Law wrote: > > > >> On 11/7/19 2:34 PM, Jozef Lawrynowicz wrote: > >>> Given that MSP430 is a resource constrained, embedded target disabling >

Re: [PATCH 1/4] MSP430: Disable TM clone registry by default

2019-11-24 Thread Jeff Law
On 11/24/19 7:20 AM, Jozef Lawrynowicz wrote: > On Sun, 17 Nov 2019 12:11:23 -0700 > Jeff Law wrote: > >> 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

Re: [PATCH 1/4] MSP430: Disable TM clone registry by default

2019-11-24 Thread Jozef Lawrynowicz
On Sun, 17 Nov 2019 12:11:23 -0700 Jeff Law wrote: > 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

Re: [PATCH 1/4] MSP430: Disable TM clone registry by default

2019-11-17 Thread Jeff Law
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 >

[PATCH 1/4] MSP430: Disable TM clone registry by default

2019-11-07 Thread Jozef Lawrynowicz
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 Date: Tue, 29 Oct 2019 14:49:08 + Subject: [PATCH 1/4] MSP430: Disable TM cl