Obviously he can't return though. Here's what I would argue for in setting a standards document:

main() { int mainvar;

newthread(t1); /* t1 is a thread and it can access mainvar... */

sub(); }

sub() { int subvar;

newthread(t2); /* t2 can access subvar or mainvar, but maybe * t1 can't access subvar. * Maybe the stack just crossed a page boundary. */

while(1) keep_stack_context(); }

Essentially threads would only be guaranteed access to stack variables both in existence and valid when the thread is created. All stack growth can be in separate address spaces.

If a stackless main() creates a bunch of threads at that level and then idles those threads would have completely disjoint stacks.

Peter

To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message