Don't assert thread_local initialization
Initialization of thread_local variables in shared libraries might be
implementation dependent.
Just keep the assert for Win32.
https://docs.microsoft.com/en-us/cpp/cpp/thread?view=vs-2019 states that
"Thread-local variables that are initialized statically with constant
values are generally initialized properly on all threads."
Bug: b/157525646
Change-Id: Ifb6a77e085c0f21f13af58c89050868992928300
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/45809
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Antonio Maiorano <amaiorano@google.com>
diff --git a/src/Reactor/SubzeroReactor.cpp b/src/Reactor/SubzeroReactor.cpp
index 030dd43..b89fb20 100644
--- a/src/Reactor/SubzeroReactor.cpp
+++ b/src/Reactor/SubzeroReactor.cpp
@@ -902,7 +902,9 @@
::routine = elfMemory;
}
+#if defined(_WIN32) // TODO(b/157525646): Initialization of thread_local variables in shared libraries may not be supported on all platforms.
ASSERT(Variable::unmaterializedVariables == nullptr);
+#endif
Variable::unmaterializedVariables = new std::unordered_set<const Variable *>();
}
