From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2936 invoked by alias); 11 Apr 2002 00:06:10 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 2914 invoked by uid 61); 11 Apr 2002 00:06:10 -0000 Date: Wed, 10 Apr 2002 17:06:00 -0000 Message-ID: <20020411000610.2913.qmail@sources.redhat.com> To: borg@ifh.de, denauroi@in2p3.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, stegmann@ifh.de From: pme@gcc.gnu.org Reply-To: pme@gcc.gnu.org, borg@ifh.de, denauroi@in2p3.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, stegmann@ifh.de, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/6227: std::string not thread safe with gcc3.0.4 on dual processor machine X-SW-Source: 2002-04/txt/msg00594.txt.bz2 List-Id: Synopsis: std::string not thread safe with gcc3.0.4 on dual processor machine State-Changed-From-To: open->feedback State-Changed-By: pme State-Changed-When: Wed Apr 10 17:06:09 2002 State-Changed-Why: Thank you for your bug report. The only MP machines available to me are Sun Ultras, and my 3.1 sources are having difficulty building on that platform. As soon as the build issues are resolved, I'll try and reproduce this there. In the meantime, you may wish to give a 3.1 snapshot a try. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6227