X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<4B06A11C.6030101@cwilson.fastmail.fm>
Date:	Fri, 20 Nov 2009 09:01:00 -0500
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.25-15: pthread_join deadlocks
References:	<20091119124405 DOT GF29173 AT calimero DOT vinschen DOT de> <4B067444 DOT 80900 AT ece DOT cmu DOT edu>
In-Reply-To:	<4B067444.80900@ece.cmu.edu>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Ryan Johnson wrote:
> Out of curiosity, how much did removing the racy optimization hurt
> performance? The patch just yanked it completely iirc. An alternative
> might be to have the main thread check for single-thread environment
> only at acquire time, and then release only if it acquired (the latter
> is probably a good idea regardles...).

The problem is, IIRC there is no such thing as a single-thread
environment for cygwin programs: every cygwin program has a secondary
thread that handles translating certain windows events into unixy
signals, or something like that. I think.

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -