This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Threads
- To: M Dipperstein <mdipper at cs dot ucsb dot edu>
- Subject: Re: Threads
- From: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Date: Fri, 4 Feb 2000 10:05:58 -0600 (CST)
- cc: cygwin at sourceware dot cygnus dot com
On Fri, 4 Feb 2000, M Dipperstein wrote:
> There have been several postings to the list which discuss pthreads and
> the lack of "thread safety" in cygwin. I was hoping somebody would
> clarify the statement that cygwin is not thread safe.
Cygwin is thread-safe by default as of 2000-01-05 or so snapshot (or
perhaps even a bit earlier). Last year, you had to build it yourself
to get the thread-safe code. It's still being worked on, so there are
bound to be problems, but seems to work ok.
> I'm developing a thread package from the QuickThreads primitives. The
> final target is not cygwin, but it's a great tool for development along
> the way. So far, there seem to be no problems using the QuickThreads
> primitives in code compiled with gcc under cygwin.
As long as it's not C++ using exception handling you should be fine. Until
we enhance the Cygwin's pthread interface, the C++ runtime is still single
threaded.
> Are the only concerns regarding thread safety related to non-reentrant code
> in the cygwin libraries? If that's the only problem, I think I don't have
> to worry. The thread package I'll be working with is cooperative, and
> will not allow for library routines to be reentered before they have
> returned.
Try it out and see what happens. We can try and fix the problems, but need
to know what those are first.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com