19 May
2013
19 May
'13
11:32 p.m.
On Fri, May 17, 2013 at 5:54 AM, Jonathan Wakely
On 17 May 2013 02:46, Tim Blechmann wrote:
hmm, maybe checks for both would be needed. e.g. some compilers have <atomic>, but don't implement it completely ... quite a mess ... so i'm rather conservative about using std::atomic (clang/libstdc++ might cause some problems) ... but enabling std::atomic via _LIBCPP_VERSION is probably safe ...
What's missing from libstdc++'s <atomic> on arm?
I believe nothing with gcc 4.8, but no arm device toolchain uses that version yet (android is on 4.6 as of March 2013). Apple's version of gcc is something horrible like 4.2.