Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID:	<005601c0b148$e2be5520$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT cygwin DOT com>
References:	<006501c0b120$094af0f0$0200a8c0 AT lifelesswks> <20010320091440 DOT G32706 AT redhat DOT com>
Subject:	Re: YANDQ
Date:	Wed, 21 Mar 2001 01:20:11 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	20 Mar 2001 14:14:40.0365 (UTC) FILETIME=[1A50F9D0:01C0B148]

----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
To: <cygwin-developers AT cygwin DOT com>
Sent: Wednesday, March 21, 2001 1:14 AM
Subject: Re: YANDQ


> On Tue, Mar 20, 2001 at 08:27:45PM +1100, Robert Collins wrote:
> >
> >Are these specs way off base? If not, how do I go about altering
> >sys/types.h (which I note appears to be part of newlib).
>
> You submit a patch to the newlib mailing list which is conditionalized
> #ifdef __CYGWIN__
> #endif
>
> I can approve patches like this as long as they don't make changes to
> any non-cygwin part of newlib.
>
> cgf
>

Great. I'll do these changes as part of the threads overhaul. I've got
the revamped code going with the minor issue that after CVS updating,
something bad has broken :[ , and it's a lot cleaner.

I think I can tell you why the arrays where there in the first place:
a) avoid testing for readable memory and
b) to implement pthread_self (gets a pthread_t referring to the current
thread).

I've implemented a) as we discussed already and b) using a Tls Index for
the local thread object.

Rob

- Raw text -