search for: getcurrentstacktop

...yasskin at google.com> wrote: > I'll forward your next draft back to the stackless folks, unless you > want to pick up the thread with them. Their reply: http://thread.gmane.org/gmane.comp.python.stackless/4464/focus=4475 Instead of @llvm.getcontextstacktop(%context), they want @llvm.getcurrentstacktop() so that they can copy the stack out before switching, and copy it back in after switching. I'm not sure this exactly works either, since before "copying the stack back", any allocas are pointing at old-frame data and so are invalid. They'd need to guarantee that any relevant dat...

...ation. Is there a "main" context that will handle all this saving and restoring of stacks? If so, does it actually share stacks with other contexts in the way they're expected to share it with each other? > > Instead of @llvm.getcontextstacktop(%context), they want > @llvm.getcurrentstacktop() so that they can copy the stack out before > switching, and copy it back in after switching. I'm not sure this > exactly works either, since before "copying the stack back", any > allocas are pointing at old-frame data and so are invalid. They'd need > to guarantee t...

On Sun, Apr 11, 2010 at 2:41 PM, Kenneth Uildriks <kennethuil at gmail.com> wrote: > On Sun, Apr 11, 2010 at 4:09 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: >> 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