Displaying 3 results from an estimated 3 matches for "work_on".
Did you mean:
work_fn
2010 Apr 12
0
[LLVMdev] Proposal: stack/context switching within a thread
I created a wiki at http://code.google.com/p/llvm-stack-switch/
Right now I just copied and formatted the document as-is... I'll go
back over it with your comments in mind soon. One more question,
which you can answer here or there:
> Point 4 is a bit confusing. Normally, it's fine for a thread to share
> some of its stack space with another thread, but your wording seems to
>
2010 Apr 12
2
[LLVMdev] Proposal: stack/context switching within a thread
...space with another thread, but your wording seems to
>> prohibit that.
>
> Really? How does that work?
void thread1() {
Foo shared_var;
queue.send(&shared_var);
int result = otherqueue.recv();
return;
}
void thread2() {
Foo* shared_var = queue.recv();
otherqueue.send(work_on(shared_var));
}
is legal with posix threads. It's just illegal to return out of a
function while its stack space is used by another thread. I've seen
this used inside a condition variable implementation, among other
places.
>> I'll forward your next draft back to the stackless f...
2010 Apr 12
4
[LLVMdev] Proposal: stack/context switching within a thread
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