Avoid fallbacking to software emulated compiler atomics, that are usually
provided by libatomic, which is not always present.
This fixes the test on NetBSD, which does not provide libatomic in base.
Paths
| Differential D87568
[compiler-rt] Avoid pulling libatomic to sanitizer tests ClosedPublic Authored by krytarowski on Sep 12 2020, 1:47 PM.
Details Summary Avoid fallbacking to software emulated compiler atomics, that are usually This fixes the test on NetBSD, which does not provide libatomic in base.
Diff Detail
Event TimelineComment Actions std::atomic_is_lock_free or an reimplementation of it (without pulling C++ runtime), testing a type and asserting that in runtime or build time that it is lockfree. https://en.cppreference.com/w/cpp/atomic/atomic_is_lock_free Comment Actions
I mean the existing compiler-rt code already has atomic_uint64_t, do we need to do something about it? vitalybuka added inline comments.
This revision is now accepted and ready to land.Sep 16 2020, 2:15 PM This revision was landed with ongoing or failed builds.Sep 17 2020, 7:04 AM Closed by commit rG69516ddd028e: [compiler-rt] Avoid pulling libatomic to sanitizer tests (authored by krytarowski). · Explain Why This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 292486 compiler-rt/lib/sanitizer_common/tests/sanitizer_atomic_test.cpp
|
Not for this patch but these tests must be TYPED_TEST_P