diff options
author | Ivan Maidanski <ivmai@mail.ru> | 2023-03-31 07:38:43 +0300 |
---|---|---|
committer | Ivan Maidanski <ivmai@mail.ru> | 2023-03-31 07:38:43 +0300 |
commit | 2c8ba251866ed12fa17fb51abfca063e2f6f717d (patch) | |
tree | ca22160560e451e92891b05db94b4fccb2246c72 /src/atomic_ops/sysdeps/gcc/riscv.h | |
parent | 92435d45beeaab3ea269190c0f6c5d77e6f1d710 (diff) | |
download | libatomic_ops-2c8ba251866ed12fa17fb51abfca063e2f6f717d.tar.gz |
Eliminate 'atomic_thread_fence is unsupported with tsan' gcc-11 warning
The workaround is to use __atomic_test_and_set instead of
__atomic_thread_fence in case of option -fsanitize=thread is passed
to gcc (or clang). The old behavior could be turned on by defining
AO_USE_ATOMIC_THREAD_FENCE macro.
* src/atomic_ops/sysdeps/gcc/generic.h [!AO_UNIPROCESSOR
&& AO_THREAD_SANITIZER && !AO_USE_ATOMIC_THREAD_FENCE] (AO_nop_read,
AO_nop_write, AO_nop_full): Do not define (using
__atomic_thread_fence); add comment.
Diffstat (limited to 'src/atomic_ops/sysdeps/gcc/riscv.h')
0 files changed, 0 insertions, 0 deletions