Displaying 3 results from an estimated 3 matches for "callmaysuspendcallback".
2014 May 13
5
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
...*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 context.
void callMaySuspendCallback();
On May 12, 2014, at 5:26 PM, Nick Lewycky <nlewycky at google.com> wrote:
> Would you (or anyone) oppose a simple maySuspendContext() callback API? It would mean nothing more than the thread(s) for a given LLVM context can be suspended independent from other contexts.
>
> I thi...
2014 May 15
3
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
...spend 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 context.
>> void callMaySuspendCallback();
>>
>> On May 12, 2014, at 5:26 PM, Nick Lewycky <nlewycky at google.com> wrote:
>>
>>> Would you (or anyone) oppose a simple maySuspendContext() callback API? It would mean nothing more than the thread(s) for a given LLVM context can be suspended independent fr...
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,