Re: 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

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

[ACTIVITY] 25-29 November 2013

2013-12-02 Thread Christophe Lyon
== Progress == * Disable peeling: - spawned benchmarking jobs using recent trunk and another older one to check for performance regressions. - locally generated the code for the same benchmark to analyze the differences * cbuildv2: - retried to create 4.8-2013.11 source release. Identified

[ACTIVITY] Week 48

2013-12-02 Thread Yvan Roux
== Issues == * None. == Progress == * LRA on AArch32: o TCWG-342 : UPSTREAM: LRA issue in gfortran with store minmaxsi - Committed as rev205526 . - Card resolved. o TCWG-344 : UPSTREAM: Thumb bootstrap failure with LRA - Committed THUMB_SECONDARY_INPUT_RELOAD_CLASS patch as rev205