Revert 'Workaround a hang in sigsuspend if compiled with Thread Sanitizer'

This reverts commit 04fd7b5309596423e4342502d3123028d836d551.

Because it does not avoid hangs in all cases when stopping the world.
A better solution is to re-enable signals in the suspend handler.

diff --git a/pthread_stop_world.c b/pthread_stop_world.c
index b30b9e16a00df1ae3316b528f009ca9ba2ce5b97..cfb4c1ae85884646abc7b731a368e0339aa73154 100644 (file)
--- a/pthread_stop_world.c
+++ b/pthread_stop_world.c
@@ -327,16 +327,7 @@ STATIC void GC_suspend_handler_inner(ptr_t dummy GC_ATTR_UNUSED,
   /* really safe to proceed.  Under normal circumstances,       */
   /* this code should not be executed.                          */
   do {
-#   ifdef THREAD_SANITIZER
-      /* TODO: A temporal workaround.  Generally, signal handlers are   */
-      /* delayed until the next call to TSan ProcessPendingSignals, the */
-      /* latter is called on interceptors, system calls, and atomic     */
-      /* operations only.  Thus, the collector hangs sometimes (as of   */
-      /* now) if the signal occurs while waiting in sigsuspend().       */
-      sched_yield();
-#   else
       sigsuspend (&suspend_handler_mask);
-#   endif
   } while (AO_load_acquire(&GC_world_is_stopped)
            && AO_load(&GC_stop_count) == my_stop_count);
   /* If the RESTART signal gets lost, we can still lose.  That should   */