Re: [PATCH] libstdc++: Allow using without lock free atomic int

2017-01-04 Thread Christophe Lyon
On 4 January 2017 at 16:10, Jonathan Wakely wrote: > On 04/01/17 16:00 +0100, Christophe Lyon wrote: >> >> Hi Jonathan, >> >> On 4 January 2017 at 12:02, Jonathan Wakely wrote: >>> >>> On 03/01/17 15:32 +, Jonathan Wakely wrote: Here's what I plan to commit to trunk tomorrow. >

Re: [PATCH] libstdc++: Allow using without lock free atomic int

2017-01-04 Thread Jonathan Wakely
On 04/01/17 16:00 +0100, Christophe Lyon wrote: Hi Jonathan, On 4 January 2017 at 12:02, Jonathan Wakely wrote: On 03/01/17 15:32 +, Jonathan Wakely wrote: Here's what I plan to commit to trunk tomorrow. Committed to trunk. After this commit (r244051), I do see improvements, but al

Re: [PATCH] libstdc++: Allow using without lock free atomic int

2017-01-04 Thread Christophe Lyon
Hi Jonathan, On 4 January 2017 at 12:02, Jonathan Wakely wrote: > On 03/01/17 15:32 +, Jonathan Wakely wrote: >> >> Here's what I plan to commit to trunk tomorrow. > > > Committed to trunk. > > After this commit (r244051), I do see improvements, but also a few new failures. The big picture is

Re: [PATCH] libstdc++: Allow using without lock free atomic int

2017-01-04 Thread Jonathan Wakely
On 03/01/17 15:32 +, Jonathan Wakely wrote: Here's what I plan to commit to trunk tomorrow. Committed to trunk.

Re: [PATCH] libstdc++: Allow using without lock free atomic int

2017-01-03 Thread Jonathan Wakely
On 19/12/16 17:52 +, Jonathan Wakely wrote: On 16/12/16 17:52 +, Jonathan Wakely wrote: On 09/11/16 23:26 +0200, Pauli wrote: Compiling programs using std::future for old arm processors fails. The problem is caused by preprocessor check for atomic lock free int. Future can be changed t

Re: [PATCH] libstdc++: Allow using without lock free atomic int

2016-12-19 Thread Jonathan Wakely
On 16/12/16 17:52 +, Jonathan Wakely wrote: On 09/11/16 23:26 +0200, Pauli wrote: Compiling programs using std::future for old arm processors fails. The problem is caused by preprocessor check for atomic lock free int. Future can be changed to work correctly without lock free atomics with m

Re: [PATCH] libstdc++: Allow using without lock free atomic int

2016-12-16 Thread Jonathan Wakely
On 09/11/16 23:26 +0200, Pauli wrote: Compiling programs using std::future for old arm processors fails. The problem is caused by preprocessor check for atomic lock free int. Future can be changed to work correctly without lock free atomics with minor changes to exception_ptr implementation. Wi

[PATCH] libstdc++: Allow using without lock free atomic int

2016-11-09 Thread Pauli
Compiling programs using std::future for old arm processors fails. The problem is caused by preprocessor check for atomic lock free int. Future can be changed to work correctly without lock free atomics with minor changes to exception_ptr implementation. Without lock free atomics there is questio