search for: thisctx

...nding to the current execution context. The ; second argument shall point to context data generated by a call to ; llvm.getcontext or llvm.makecontext. Execution will transfer to the context ; specified by pNewCtx. Using llvm.swapcontext or llvm.setcontext to set ; the context to that stored in pThisCtx will cause execution to transfer back ; 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({}* %th...

...nding to the current execution context. The ; second argument shall point to context data generated by a call to ; llvm.getcontext or llvm.makecontext. Execution will transfer to the context ; specified by pNewCtx. Using llvm.swapcontext or llvm.setcontext to set ; the context to that stored in pThisCtx will cause execution to transfer back ; 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,...

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