[K/N] Use SpinLock for GlobalData::init() on Windows

There is a weird bug on Windows when sometimes GlobalData has started
initialization and created the timer thread for the GC scheduler;
but when the timer thread tries to wait for the GlobalData
initialization to finish, it crashes on trying to lock the
synchronization mutex. GlobalData initialization does successfully
take the synchronization mutex, so the mutex should definitely be
initialized.

Replace std::mutex with SpinLock on Windows to workaround the problem.

^KT-71644

Author: projedi

kotlin-native/runtime/src/mm/cpp/GlobalData.cpp

@@ -11,6 +11,10 @@
 #include "CompilerConstants.hpp"
 #include "Porting.h"
 
+#if KONAN_WINDOWS
+#include "concurrent/Mutex.hpp"
+#endif
+
 using namespace kotlin;
 
 namespace {
@@ -33,8 +37,17 @@ std::atomic<InitState> globalDataInitState = InitState::kUninitialized;
 std::atomic<std::thread::id> globalDataInitializingThread{};
 ManuallyScoped<mm::GlobalData> globalDataInstance{};
 
+#if KONAN_WINDOWS
+// On winpthreads, there's a weird bug if this is a regular `std::mutex`:
+// even though `constructGlobalDataInstance()` has already started (and so,
+// has already successfully tried locking this mutex), `waitGlobalDataInitialized`
+// may crash trying to lock it too.
+SpinLock globalDataInitMutex;
+std::condition_variable_any globalDataInitCV;
+#else
 std::mutex globalDataInitMutex;
 std::condition_variable globalDataInitCV;
+#endif
 
 void constructGlobalDataInstance() noexcept {
     std::unique_lock guard{globalDataInitMutex};