caio/clang-p2996
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[libc++] Fix broken stdatomic test on GCC

Browse Source 
The test would trigger -Wtautological-compare. I think that the little
we gain from comparing addresses isn't worth the added complexity to
work around the warning.
This commit is contained in:
Louis Dionne
2022-02-15 09:25:29 -05:00
parent 2808743cbd
commit a30a7948d5
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
libcxx/test/std/atomics/stdatomic.h.syn/types.compile.pass.cpp
View File

@@ -142,12 +142,12 @@ void f() {
static_assert(std::is_same_v<std::atomic<const long>, _Atomic(const long)>);
static_assert(std::is_same_v<std::memory_order, ::memory_order>);
static_assert(&std::memory_order_relaxed == &::memory_order_relaxed);
static_assert(&std::memory_order_consume == &::memory_order_consume);
static_assert(&std::memory_order_acquire == &::memory_order_acquire);
static_assert(&std::memory_order_release == &::memory_order_release);
static_assert(&std::memory_order_acq_rel == &::memory_order_acq_rel);
static_assert(&std::memory_order_seq_cst == &::memory_order_seq_cst);
static_assert(std::memory_order_relaxed == ::memory_order_relaxed);
static_assert(std::memory_order_consume == ::memory_order_consume);
static_assert(std::memory_order_acquire == ::memory_order_acquire);
static_assert(std::memory_order_release == ::memory_order_release);
static_assert(std::memory_order_acq_rel == ::memory_order_acq_rel);
static_assert(std::memory_order_seq_cst == ::memory_order_seq_cst);
static_assert(std::is_same_v<std::atomic_flag, ::atomic_flag>);