Re-write the pthread thread-local storage portability layer to be backed by Boost
Summary: Boost handles ensuring destruction order is correct far better than the implementation previously being used. This gets the Windows build working again, as it's currently hitting a thread-local static destruction order issue. Specifically, the thread_local containing the backing map for the portability implementation was being destroyed before a thread_local in rcu, which caused attempts to access thread local values that had already been freed. Reviewed By: yfeldblum Differential Revision: D7312978 fbshipit-source-id: 4d7f1f4d8bb0b92e0c52366078ee7ee34c4248f2
Showing
Please register or sign in to comment