28 Feb
2014
28 Feb
'14
5:51 p.m.
On 28/02/14 18:11, John Maddock wrote:
The libc++ config header, libcpp.hpp, always defines BOOST_NO_CXX11_HDR_ATOMIC, but the libc++ that - I presume - ships with "Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)" appears to have a functional <atomic>.
Do you have a patch that identifies when we don't need to set that macro?
should the macro declare that the header exists, or that the implementation is complete? e.g. gcc/libstdc++ did support atomic<Integral> before fully supporting atomic<>. likewise, clang/libc++ is broken, if the wrapped type is a trivially copyable class [1]. tim [1] http://llvm.org/bugs/show_bug.cgi?id=18097