Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Thu, 6 Mar 2003 11:40:06 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: gcc static constructor multi-threading flaw
Message-ID: <20030306164006.GA7339@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <3E4D06B8 DOT 5010306 AT hekimian DOT com> <20030305050809 DOT GB29712 AT redhat DOT com> <3E677447 DOT 80202 AT hekimian DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E677447.80202@hekimian.com>
User-Agent: Mutt/1.5.1i

On Thu, Mar 06, 2003 at 11:16:07AM -0500, Joe Buehler wrote:
>Christopher Faylor wrote:
>>Since neither gcc nor newlib have responded to this problem, I've added
>>a wrapper in cygwin.  It will be in 1.3.21.
>
>By the way, if I recall correctly, the real fix *has* to be made in
>gcc.  There is still a race in the gcc-generated code that can cause
>double-destruction at process exit.

I am sure that this is the case.  I'm not going to change gcc, though.

cgf