Remove gcc-13 from tsan

test/Jamfile

@@ -93,9 +93,7 @@ local requirements =
         <toolset>msvc:<define>_SILENCE_CXX17_ADAPTOR_TYPEDEFS_DEPRECATION_WARNING
         <toolset>msvc:<define>_SILENCE_CXX17_ITERATOR_BASE_CLASS_DEPRECATION_WARNING
         # GCC13 doesn't understand view types and issues array bound warnings that don't make sense.
-        # TSAN complains about std::atomic_thread_fence not being correctly supported, which
-        # is used by Asio. In principle, it doesn't look like it affects tsan reports, so suppress the warning
-        <toolset>gcc-13:<cxxflags>-Wno-dangling-reference,-Wno-array-bounds,-Wno-tsan
+        <toolset>gcc-13:<cxxflags>-Wno-dangling-reference,-Wno-array-bounds
         <target-os>linux:<define>_XOPEN_SOURCE=600
         <target-os>linux:<define>_GNU_SOURCE=1
         <target-os>windows:<define>_WIN32_WINNT=0x0601

test/thread_safety/Jamfile

@@ -17,10 +17,12 @@ if $(hostname) = ""
 # TSAN can't be enabled in our ARM CIs, since they fail
 # the personality() syscall to disable address space layout randomization.
 # In OSX, tsan reports a race condition in Asio's kqueue reactor. Ignore this for now.
+# gcc-13 complains about TSAN not supporting std::atomic_thread_fence, which is used by Asio.
+# However, this doesn't seem to affect TSAN results
 rule tsan_if_not_arm ( properties * )
 {
     local result ;
-    if ! <architecture>arm in $(properties) && ! <target-os>darwin in $(properties)
+    if ! <architecture>arm in $(properties) && ! <target-os>darwin in $(properties) && ! <toolset>gcc-13 in $(properties)
     {
         result += <thread-sanitizer>norecover ;
     }