This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: pthreads status? [was Re: [Fwd: Many changes in latest snapshot]]
- To: "cygwin-developers at sourceware dot cygnus dot com" <cygwin-developers at sourceware dot cygnus dot com>
- Subject: Re: pthreads status? [was Re: [Fwd: Many changes in latest snapshot]]
- From: John Fortin <fortinj at ibm dot net>
- Date: Tue, 07 Dec 1999 20:44:48 -0500
- References: <199912072147.PAA11869@mercury.xraylith.wisc.edu>
Mumit,
Here are the various pthread functions defined in cygwin.din.
The 2 major file for pthread implementation are pthread.cc, thread.cc
There are also thread.h and include/pthread.h include files.
Hope this helps
pthread_create JEF
pthread_attr_init ? Handles only stacksize
pthread_attr_destroy ? "" "" ""
pthread_attr_setstacksize ?
pthread_attr_getstacksize ?
pthread_exit JEF
pthread_join JEF
pthread_detach JEF
pthread_suspend JEF
pthread_continue JEF
pthread_key_create NO
pthread_key_delete NO
pthread_setspecific NO
pthread_getspecific NO
pthread_kill JEF
pthread_sigmask ?
pthread_self JEF
pthread_equal JEF
pthread_mutex_init ?
pthread_mutex_lock ?
pthread_mutex_unlock ?
pthread_mutex_destroy ?
sem_init ?
sem_destroy ?
sem_wait ?
sem_trywait ?
sem_post ?
Where:
NO = not implemented
JEF = some initial testing by me
? = implemented, but not tested by me.
Mumit Khan wrote:
>
> John Fortin <fortinj@ibm.net> writes:
> >
> > Since I've added some of the functionality for pthreads, please keep me
> > in the loop.
> > I've not been working on it much due to the xfree86 port, but if this is
> > starting to take off, I can make time.
> >
>
> Right now I'm trying to figure out how pthreads is glued onto Cygwin, and
> also trying to figure out exactly what's missing. I have a few thousand
> errors messages to go through from my last attempt to build a reasonably
> MT-heavy multi-threaded tool; most of these error messages are bound to
> be cascades from missing type definitions etc.
>
> John, can you or someone else involved summarize quickly exactly what is
> there and what is not? That will really cut down on the hunt and fix
> time.
>
> Regards,
> Mumit