![]() We never noticed it because our CI doesn't actually build against a C library that doesn't have threading functionality, however building against a truly thread-free platform surfaces these issues. Differential Revision: https://reviews.llvm.org/D114242 |
||
---|---|---|
.. | ||
thread.once.callonce | ||
thread.once.onceflag |