Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <037701c0c3ab$9049bf30$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin AT cygwin DOT com>
Subject: pthreads update for the adventurous
Date: Fri, 13 Apr 2001 09:51:57 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 1
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 12 Apr 2001 23:45:14.0990 (UTC) FILETIME=[9F3E70E0:01C0C3AA]

This is a followup to the long thread early this week about g++
exception handling crashing with a sigsegv.

I've implemented the necessary functions to build the cygwin gcc
2.95.3-2 source tarball with posix thread support. The resulting gcc,
when building the test case (using sched_yield as that forced the fault)
does not crash or fault in any way (that I could see).

Snapshots with a date greater that 2001-Apr-10 have the new
functionality. The new functionality includes all of the pthread_*
functions from the single unix specification with two exceptions:
pthread_atfork & static initializers. Static initializers for mutex's
exist, and will be introduced for other objects in due course.

Cancellation point functions are present, but at the moment are just
stubs: cancellation points will require a substantial amount of work
across all of the cygwin library functions... so they'll be coming in
later.

This is a plea for testing. On this list we've seen discussions about
pthreads for
g++,
gcj,
miniORB,
python
and who knows what else in the past.

If you are regularly rolling your own with any of those three
applications, please test the latest snapshot (available anytime now)
and report back any errors or hiccups. I suspect the appropriate list
for feedback is the cygwin-apps list - I'm posting here because most of
the discussions took place here.

Special note: g++ testing requires rebuilding gcc to take advantage of
threads. ONLY DO THIS IF YOU"VE DONE IT BEFORE. I'm not familiar with
the innards of gcc and thus not able to help you out of any problems
that may occur.

There is some minor urgency on this: I would really like to hear back on
any issues with the pthreads code before Chris freezes cygwin and rolls
1.3.0 - which is only a few days away.

Finally, IIRC GCJ was foundering on some sort of threads-related issue.
It'd be great if someone could look into that with the new snapshot.

Rob


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple