Bug#727621: armv5 and ATOMIC_INT_LOCK_FREE

2013-12-03 Thread Yvan Roux
According to this bugzilla entry, the issue is how ATOMIC_INT_LOCK_FREE is computed, which is not the same as the for the __atomic_always_lock_free builtin (I checked on armv5 the builtin is true for int whereas the macro value is 1). There is a proposed patch, but it still has some issues... ha

Bug#727621: armv5 and ATOMIC_INT_LOCK_FREE

2013-12-03 Thread Yvan Roux
On 3 December 2013 01:19, Nicolas Pitre wrote: > On Mon, 2 Dec 2013, Riku Voipio wrote: > >> Hi, >> >> According the debian bug report [1], it is not possible to use std::future >> on armv5 targetting toolchains. This is because libstdc++ will only enable >> std::future if ATOMIC_INT_LOCK_FREE > 1

Bug#727621: armv5 and ATOMIC_INT_LOCK_FREE

2013-12-02 Thread Nicolas Pitre
On Mon, 2 Dec 2013, Riku Voipio wrote: > Hi, > > According the debian bug report [1], it is not possible to use std::future > on armv5 targetting toolchains. This is because libstdc++ will only enable > std::future if ATOMIC_INT_LOCK_FREE > 1. There is no LDREX for armv5 and > older, so this def

Bug#727621: armv5 and ATOMIC_INT_LOCK_FREE

2013-12-02 Thread Riku Voipio
Hi, According the debian bug report [1], it is not possible to use std::future on armv5 targetting toolchains. This is because libstdc++ will only enable std::future if ATOMIC_INT_LOCK_FREE > 1. There is no LDREX for armv5 and older, so this definition is set to ATOMIC_INT_LOCK_FREE when compilin