From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11554 invoked by alias); 2 Apr 2002 02:56:23 -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 11534 invoked by uid 61); 2 Apr 2002 02:56:22 -0000 Date: Mon, 01 Apr 2002 18:56:00 -0000 Message-ID: <20020402025622.11533.qmail@sources.redhat.com> To: eric.norum@usask.ca, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: bkoz@gcc.gnu.org Reply-To: bkoz@gcc.gnu.org, eric.norum@usask.ca, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/4367: Sparc atomicity.h routines can lock up on some OS. X-SW-Source: 2002-04/txt/msg00025.txt.bz2 List-Id: Synopsis: Sparc atomicity.h routines can lock up on some OS. State-Changed-From-To: open->analyzed State-Changed-By: bkoz State-Changed-When: Mon Apr 1 18:56:21 2002 State-Changed-Why: I guess you'll have to use heavier-weight locks for these OS's. Can you think of another solution? I cannot. Note this is an issue with all the cpu/atomicity.h files, not just sparc, right? -benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4367