maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Fix GCC handling of ATOMIC_VAR_INIT 

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.

llvm-svn: 333327
This commit is contained in:
JF Bastien 2018-05-26 00:13:53 +00:00
parent 8419cf307e
commit 925faf274c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -17,8 +17,8 @@
#include <atomic>
int main() {
std::atomic<int> ai = ATOMIC_VAR_INIT(0);
volatile std::atomic<int> vai = ATOMIC_VAR_INIT(0);
std::atomic<int> ai;
volatile std::atomic<int> vai;
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}}