Displaying 3 results from an estimated 3 matches for "prevctx".
Did you mean:
prev_ctx
2010 Apr 07
2
[LLVMdev] Proposal: stack/context switching within a thread
...; to this context as if from a return from llvm.swapcontext. The linked
; context pointer corresponding to %pThisCtx is not modified.
declare void llvm.swapcontext({}* %pThisCtx, {}* %pNewCtx)
A simple example using these intrinsics:
define void @co1({}* %thisCtx, {}* %data) nounwind {
entry:
%prevCtx = call {}* @llvm.getlinkcontext(%thisCtx)
; Now call print messages. After each print message, temporarily yield
; control back to the previous context.
call void @printCo1FirstMessage()
call void @llvm.swapcontext({}* %thisCtx, {}* %prevCtx)
call void @printCo1SecondMessage()
call vo...
2010 Apr 11
0
[LLVMdev] Proposal: stack/context switching within a thread
...ck
; to this context as if from a return from llvm.swapcontext. The linked
; context pointer stored in %pThisCtx is not modified.
declare void llvm.swapcontext({}* %pThisCtx, {}* %pNewCtx)
A simple example using these intrinsics:
define void @co1({}* %thisCtx, i32 %startVal) nounwind {
entry:
%prevCtx = call {}* @llvm.getlinkcontext(%thisCtx)
; Now call print messages. After each print message, temporarily yield
; control back to the previous context.
call void @printCo1FirstMessage(i32 %startVal)
call void @llvm.swapcontext({}* %thisCtx, {}* %prevCtx)
call void @printCo1SecondMessag...
2010 Apr 11
3
[LLVMdev] Proposal: stack/context switching within a thread
Kenneth Uildriks <kennethuil at gmail.com> wrote:
> As I see it, the context switching mechanism itself needs to know
> where to point the stack register when switching. The C routines take
> an initial stack pointer when creating the context, and keep track of
> it from there. If we don't actually need to interoperate with
> contexts created from the C routines, we have