Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 11 Apr 2001 19:31:18 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: mumit: gcc advice please Message-ID: <20010411193118.C30206@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <01a001c0c28b$2cfec270$0200a8c0 AT lifelesswks> <02f301c0c2dc$bed61a30$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <02f301c0c2dc$bed61a30$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, Apr 12, 2001 at 09:11:17AM +1000 On Thu, Apr 12, 2001 at 09:11:17AM +1000, Robert Collins wrote: >Thanks Mumit, I caught that myself immediately after posting... I didn't >repost as there were more questions there. > >The good news is: >It seems to work. > >The test case that was dying is no longer dying, and it uses >pthread_key's and pthread_once both of which are fully operation here. >(well, barring cancellation points as previously mentioned. > >So I'm going to clean up my code a little, and then post an interim >patch to cygwin-patches for any adventure seeking folk. Once you do this, I'll give your stuff a couple of days to settle down and then I'll create a brand-new 1.3.0 release. I'll be willing to lay bets right now that it will be followed by a 1.3.1 release very soon thereafter because I'm sure there is something stupid lurking in the wings (like the recent "I can't run a .bat file problem") but I think that enough people are expressing satisfaction with recent snapshots that we should be in *relatively* good shape. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple