From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9264 invoked by alias); 1 Jun 2002 01:05:21 -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 9243 invoked by uid 61); 1 Jun 2002 01:05:20 -0000 Date: Fri, 31 May 2002 18:09:00 -0000 Message-ID: <20020601010520.9242.qmail@sources.redhat.com> To: acnrf@dial.eunet.ch, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rearnsha@arm.com, robin.farine@terminus.org From: pme@gcc.gnu.org Reply-To: pme@gcc.gnu.org, acnrf@dial.eunet.ch, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rearnsha@arm.com, robin.farine@terminus.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/3584: arm-specific atomic operations not atomic X-SW-Source: 2002-05/txt/msg01034.txt.bz2 List-Id: Synopsis: arm-specific atomic operations not atomic State-Changed-From-To: open->feedback State-Changed-By: pme State-Changed-When: Fri May 31 18:05:20 2002 State-Changed-Why: What's the status of this PR? How are things for 3.1 and 3.2? > I'm not up on what threading models are usable with > libstdc++-v3, so I'll have to leave that side of > things to the c++ library maintainers. We simply grab whatever thread model has been configured for GCC, as represented by the various gcc/gthr-*.h files. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3584