Displaying 1 result from an estimated 1 matches for "do_on_stack_replacement".
2015 Mar 19
3
[LLVMdev] How will OrcJIT guarantee thread-safety when a function is asked to be re generated?
Hi Sanjoy,
> You need the hijack-return-pc approach *in addition* to a call-site
> patching approach. Modifying the return PC lets you guarantee that
> nothing will *return* into the old generated code. To guarantee that
> nothing will *call* into it either you could use a double indirection
> (all calls go through a trampoline) or patchpoints.
You need to hijack the return