![]() If mutex::try_lock() is called in a thread that already owns the mutex, the behavior is undefined. The patch fixes the issue by creating another thread, where the call is allowed. Differential Revision: https://reviews.llvm.org/D94656 |
||
---|---|---|
.. | ||
thread.lock.guard | ||
thread.lock.scoped | ||
thread.lock.shared | ||
thread.lock.unique | ||
types.fail.cpp | ||
types.pass.cpp |