|Info needed (Sparc C compiler w/o register window) clim@ICSI.Berkeley.EDU (1992-04-14)|
|No threads on SPARC? (was Re: Info needed (Sparc C compiler w/o regist firstname.lastname@example.org (1992-04-17)|
|Re: No threads on SPARC? email@example.com (1992-04-20)|
|From:||firstname.lastname@example.org (David Keppel)|
|Organization:||Computer Science & Engineering, U. of Washington, Seattle|
|Date:||Mon, 20 Apr 1992 19:27:32 GMT|
>email@example.com (David Keppel) writes:
>> [Y]ou can't write a truly user-space threads package on the SPARC ...
firstname.lastname@example.org (Frank Mueller) writes:
>I disagree, I implemented a stripped-down version of preemtive Pthreads
>using library implementation techniques.
To clarify (summarizing from e-mail w/ Frank Mueller): a threads package
for code built with the standard C compiler needs to trap to the kernel to
flush the windows on a thread context swap.
The thread scheduling decisions and saving and restoring of ``obvious''
processor state are done in the user space. Thus, the threads package can
be considered user-space, and can be customized and optimized for the
application, etc. However, the kernel trap is still needed, so I consider
the SPARC threads packages I've written to be not truly user-space.
;-D oN ( A terminology-space threads package ) Pardo
Return to the
Search the comp.compilers archives again.