From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6644 invoked by alias); 11 Apr 2002 21:46:04 -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 6628 invoked by uid 71); 11 Apr 2002 21:46:02 -0000 Date: Thu, 11 Apr 2002 14:46:00 -0000 Message-ID: <20020411214602.6627.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Mathieu de Naurois Subject: Re: libstdc++/6227: std::string not thread safe with gcc3.0.4 on dual processor machine Reply-To: Mathieu de Naurois X-SW-Source: 2002-04/txt/msg00633.txt.bz2 List-Id: The following reply was made to PR libstdc++/6227; it has been noted by GNATS. From: Mathieu de Naurois To: jakub@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 Cc: Subject: Re: libstdc++/6227: std::string not thread safe with gcc3.0.4 on dual processor machine Date: Thu, 11 Apr 2002 23:20:15 +0200 (CEST) We downloaded the 3.1 branch today and we agree: the problem is fixed for us as well. Thank you for your quick answer. Christian Stegmann & Mathieu de Naurois On 11 Apr 2002 jakub@gcc.gnu.org wrote: > Synopsis: std::string not thread safe with gcc3.0.4 on dual processor machine > > State-Changed-From-To: feedback->analyzed > State-Changed-By: jakub > State-Changed-When: Thu Apr 11 03:52:09 2002 > State-Changed-Why: > I cannot reproduce it on 3.1 branch. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6227 >