aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorHans-Peter Nilsson <hp@axis.com>2023-10-04 04:16:18 +0200
committerHans-Peter Nilsson <hp@bitrange.com>2023-10-13 02:20:30 +0200
commitba0cde8ba2d93b7193050eb5ef3cc6f7a2cdfe61 (patch)
treeee197f14dce4060b33cd9fac8fd5770be063e015 /gcc
parent2a4d9e4f533c77870cc0eb60fbbd8047da4c7386 (diff)
downloadgcc-ba0cde8ba2d93b7193050eb5ef3cc6f7a2cdfe61.zip
gcc-ba0cde8ba2d93b7193050eb5ef3cc6f7a2cdfe61.tar.gz
gcc-ba0cde8ba2d93b7193050eb5ef3cc6f7a2cdfe61.tar.bz2
testsuite: Replace many dg-require-thread-fence with dg-require-atomic-cmpxchg-word
These tests actually use a form of atomic compare and exchange operation, not just atomic loading and storing. Some targets (not supported by e.g. libatomic) have atomic loading and storing, but not compare and exchange, yielding linker errors for missing library functions. This change is just for existing uses of dg-require-thread-fence. It does not fix any other tests that should also be gated on dg-require-atomic-cmpxchg-word. * testsuite/29_atomics/atomic/compare_exchange_padding.cc, testsuite/29_atomics/atomic_flag/clear/1.cc, testsuite/29_atomics/atomic_flag/cons/value_init.cc, testsuite/29_atomics/atomic_flag/test_and_set/explicit.cc, testsuite/29_atomics/atomic_flag/test_and_set/implicit.cc, testsuite/29_atomics/atomic_ref/compare_exchange_padding.cc, testsuite/29_atomics/atomic_ref/generic.cc, testsuite/29_atomics/atomic_ref/integral.cc, testsuite/29_atomics/atomic_ref/pointer.cc: Replace dg-require-thread-fence with dg-require-atomic-cmpxchg-word.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions