Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 14 Feb 2003 11:04:44 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: gcc static constructor multi-threading flaw Message-ID: <20030214160444.GC18782@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> <20030214151314 DOT GA18458 AT redhat DOT com> <3E4D09CD DOT 1000709 AT hekimian DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E4D09CD.1000709@hekimian.com> User-Agent: Mutt/1.5.1i On Fri, Feb 14, 2003 at 10:22:53AM -0500, Joe Buehler wrote: >Christopher Faylor wrote: > >>If this is a general gcc issue, then you should ping the gcc mailing list. > >I had the discussion on the gcc list some time ago. E.g.: > >http://gcc.gnu.org/ml/gcc/2002-08/msg00248.html > >Do you want me to ping them again? Sure. Pinging is the only way this kind of stuff gets done, unfortunately. cgf