{make,set,swap}context broken on powerpc32

Ulrich Drepper drepper@redhat.com
Wed Dec 13 01:42:00 GMT 2006


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 ❖



More information about the Libc-alpha mailing list