Displaying 3 results from an estimated 3 matches for "maysuspendcallbackty".
2014 May 13
5
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
...nt that invoked the LLVM compilation. The client
/// is not garantueed to ever receive this callback. It is at the sole
/// discretion of LLVM to do so and only if it can guarantee that suspending
/// the thread won't block any forward progress in other LLVM contexts.
void setMaySuspendCallback(MaySuspendCallbackTy Callback, void *OpaqueHandle);
/// \brief Calls the may-suspend callback (if applicable).
///
/// This transfers control back to the client, which may suspend the current
/// thread. Only call this method when LLVM doesn't hold any global mutex or
/// cannot block the execution in another LLVM...
2014 May 15
3
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
.... The client
>> /// is not garantueed to ever receive this callback. It is at the sole
>> /// discretion of LLVM to do so and only if it can guarantee that suspending
>> /// the thread won't block any forward progress in other LLVM contexts.
>> void setMaySuspendCallback(MaySuspendCallbackTy Callback, void *OpaqueHandle);
>>
>> /// \brief Calls the may-suspend callback (if applicable).
>> ///
>> /// This transfers control back to the client, which may suspend the current
>> /// thread. Only call this method when LLVM doesn't hold any global mutex or
&...
2014 May 13
3
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
On May 12, 2014, at 3:52 PM, Philip Reames <listmail at philipreames.com> wrote:
> I don't have a strong opinion on this topic at the moment, but given that it is potentially GC related, I figured I'd speak up.
>
> I see two unspoken assumptions in the thread so far:
> - The runtime needs a means to bring all threads to a stop to perform some action. In particular,