From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23894 invoked by alias); 16 Jan 2002 01:36:09 -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 23862 invoked by uid 61); 16 Jan 2002 01:36:08 -0000 Date: Tue, 15 Jan 2002 17:36:00 -0000 Message-ID: <20020116013608.23861.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, markus.breuer@materna.de, nobody@gcc.gnu.org From: ljrittle@gcc.gnu.org Reply-To: ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, markus.breuer@materna.de, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org X-Mailer: gnatsweb 2.9.3 Subject: Re: libstdc++/5347: implementation is not thread-safe on multi-processor machines X-SW-Source: 2002-01/txt/msg00581.txt.bz2 List-Id: Synopsis: implementation is not thread-safe on multi-processor machines Responsible-Changed-From-To: unassigned->ljrittle Responsible-Changed-By: ljrittle Responsible-Changed-When: Tue Jan 15 17:36:08 2002 Responsible-Changed-Why: Mine. State-Changed-From-To: open->closed State-Changed-By: ljrittle State-Changed-When: Tue Jan 15 17:36:08 2002 State-Changed-Why: Duplicate of libstdc++/5037 (which is closed since it is fixed on mainline for 3.1 and, if ever released, 3.0.4+). I have tested this case against a patched copy of gcc 3.0.3 on an MP sparc and it works without crashing. I have attached the patch against gcc-3.0.3. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5347