mirror of
https://github.com/RPCS3/llvm.git
synced 2024-12-22 12:08:33 +00:00
9bc1b73c9e
Sometimes a LLVM compilation may take more time then a client would like to wait for. The problem is that it is not possible to safely suspend the LLVM thread from the outside. When the timing is bad it might be possible that the LLVM thread holds a global mutex and this would block any progress in any other thread. This commit adds a new yield callback function that can be registered with a context. LLVM will try to yield by calling this callback function, but there is no guaranteed frequency. LLVM will only do so if it can guarantee that suspending the thread won't block any forward progress in other LLVM contexts in the same process. Once the client receives the call back it can suspend the thread safely and resume it at another time. Related to <rdar://problem/16728690> git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@208945 91177308-0d34-0410-b5e6-96231b3b80d8 |
||
---|---|---|
.. | ||
Transforms | ||
Analysis.h | ||
BitReader.h | ||
BitWriter.h | ||
Core.h | ||
Disassembler.h | ||
ExecutionEngine.h | ||
Initialization.h | ||
IRReader.h | ||
Linker.h | ||
LinkTimeOptimizer.h | ||
lto.h | ||
Object.h | ||
Support.h | ||
Target.h | ||
TargetMachine.h |