Re: {make,set,swap}context broken on powerpc32

[Ulrich Drepper <drepper at redhat dot com>]

Daniel Jacobowitz wrote:
> If you getcontext in one thread and setcontext in another, even if you
> leave r2 alone, aren't you going to have other subtler problems?  I
> doubt GCC expects function calls to clobber the address of __thread
> variables.

Then your code is broken.  It must be possible to use contexts in 
different threads.  Since this is all explicit scheduling it's easy 
enough to avoid constructs where the generated code depends on __thread 
not changing.  For explicit __thread variables it is the programmer's 
responsibility to avoid them.

--
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â