This ticket is an umbrella ticket for investigating the long term solution for dealing with TSAN warnings caused by standalone barriers. As for the moment of the ticket creation, TSAN doesn't support standalone fences so they could cause false positive warnings.

However the TSAN tool is still actively developing and there is an external contribution initiative to bring standalone fences support there: https://github.com/llvm/llvm-project/pull/142579

Short-term solutions for handling warnings caused by poor support for standalone barriers were:
 • Using the TSAN annotation API
 • Suppressing the warnings

However, both of these options are supposed to tagged with a FIXME comment linked to this ticket. The scope of this ticket is to remove the suppressions and annotations once TSAN starts supporting barriers and check that there are no new warnings reported.

It also might be required to replace the current WT barriers API with C11 or GCC ones when running under TSAN since they are supposed to be instrumented (or to instrument the existing one).

Another option might be to try this PR TSAN improvement even before it gets to the compiler upstream, but first we should collect all the barrier warnings in one place.