llvm/libcxx
1
0
Fork 0
mirror of https://github.com/llvm-mirror/libcxx.git synced 2025-10-25 04:56:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix GCC handling of ATOMIC_VAR_INIT

Browse Source 
r333325 from D47225 added warning checks, and the test was written to be C++11 correct by using ATOMIC_VAR_INIT (note that the committee fixed that recently...). It seems like GCC can't handle ATOMIC_VAR_INIT well because it generates 'type 'std::atomic<int>' cannot be initialized with an initializer list' on bot libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03. Drop the ATOMIC_VAR_INITs since they weren't required to test the diagnostics.

git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@333327 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
JF Bastien
2018-05-26 00:13:53 +00:00
parent 8bacb9422b
commit 895c4f3ec7
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
test/libcxx/atomics/diagnose_nonnull.fail.cpp
View File

@@ -17,8 +17,8 @@
#include <atomic> #include <atomic>
int main() { int main() {
std::atomic<int> ai = ATOMIC_VAR_INIT(0); std::atomic<int> ai;
volatile std::atomic<int> vai = ATOMIC_VAR_INIT(0); volatile std::atomic<int> vai;
int i = 42; int i = 42;
atomic_is_lock_free((const volatile std::atomic<int>*)0); // expected-error {{null passed to a callee that requires a non-null argument}} atomic_is_lock_free((const volatile std::atomic<int>*)0); // expected-error {{null passed to a callee that requires a non-null argument}}