Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Date: Wed, 11 Apr 2001 20:10:00 -0400
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: mumit: gcc advice please
Message-ID: <20010411201000.B30651@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <01a001c0c28b$2cfec270$0200a8c0@lifelesswks> <02f301c0c2dc$bed61a30$0200a8c0@lifelesswks> <20010411193118.C30206@redhat.com> <037601c0c2e1$ff019da0$0200a8c0@lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <037601c0c2e1$ff019da0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, Apr 12, 2001 at 09:48:52AM +1000

On Thu, Apr 12, 2001 at 09:48:52AM +1000, Robert Collins wrote:
>Don't be too hopeful! I'm not claiming that this initial code is
>complete, bug free or race free.  All I'm claiming is that the ABI
>should be static from here on in, and that bugs as and when they are
>reported will be looked at.  As a matter of fact there will be some
>_known races_ in my initial code.  However I feel that getting the
>support out there, and compile problems etc reported is better than
>shooting for a perfect implementation from day 1.

Yeah, I wasn't expecting perfection.  I think we're both on the same
page, on this.  I'm sure that I've screwed up something somewhere
myself.

It makes sense to release this and get people playing with it ASAP.
Then you will have a nice spike in email activity as people find
all sorts of problems in your implementation.

One thing that just occurred to me is that "someone" should run the
Cygwin test suite prior to my release.  I guess it's time I learned
how to do that.

Are there any pthread test suites out there that could be integrated
into cygwin?

cgf

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