Howard Hinnant da9ca0b405 Stephan Tolksdorf: fixes the issue in the <atomic> header and adds corresponding tests. I've used macros to fall back to a user-provided default constructor if _LIBCPP_HAS_NO_DEFAULTED_FUNCTIONS (though I suspect that there won't be many users defining that macro). ... The tests use placement new to check that atomic values get properly zero-initialized. I had to modify the atomic_is_lock_free test, because default initialization of an object of const type 'const A' (aka 'const atomic<int>') requires a user-provided default constructor. llvm-svn: 180945		2013-05-02 20:18:43 +00:00
..
atomic_flag_clear.pass.cpp	license change	2010-11-16 22:09:02 +00:00
atomic_flag_clear_explicit.pass.cpp	license change	2010-11-16 22:09:02 +00:00
atomic_flag_test_and_set.pass.cpp	license change	2010-11-16 22:09:02 +00:00
atomic_flag_test_and_set_explicit.pass.cpp	license change	2010-11-16 22:09:02 +00:00
clear.pass.cpp	license change	2010-11-16 22:09:02 +00:00
copy_assign.fail.cpp	license change	2010-11-16 22:09:02 +00:00
copy_ctor.fail.cpp	license change	2010-11-16 22:09:02 +00:00
copy_volatile_assign.fail.cpp	license change	2010-11-16 22:09:02 +00:00
default.pass.cpp	Stephan Tolksdorf: fixes the issue in the <atomic> header and adds corresponding tests. I've used macros to fall back to a user-provided default constructor if _LIBCPP_HAS_NO_DEFAULTED_FUNCTIONS (though I suspect that there won't be many users defining that macro).	2013-05-02 20:18:43 +00:00
init.pass.cpp	license change	2010-11-16 22:09:02 +00:00
test_and_set.pass.cpp	license change	2010-11-16 22:09:02 +00:00