Re: libstdc++/5594: m68k/bits/atomicity.h unsafe on some OS/CPUcombinations

Re: libstdc++/5594: m68k/bits/atomicity.h unsafe on some OS/CPUcombinations

[Eric Norum]

The following reply was made to PR libstdc++/5594; it has been noted by GNATS.

From: Eric Norum <eric.norum@usask.ca>
To: rodrigc@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/5594: m68k/bits/atomicity.h unsafe on some 
 OS/CPUcombinations
Date: Mon, 18 Feb 2002 09:15:38 -0600

 rodrigc@gcc.gnu.org wrote:
 > 
 > Synopsis: m68k/bits/atomicity.h unsafe on some OS/CPU combinations
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: rodrigc
 > State-Changed-When: Sun Feb 17 19:35:35 2002
 > State-Changed-Why:
 >     Does the following patch address your concerns?
 >     http://gcc.gnu.org/ml/gcc-patches/2002-02/msg00942.html
 > 
 >     It has been recently applied to the main CVS head.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5594
 
 Yes, that fixes things up correctly on RTEMS.
 
 I'm pretty sure that the
 #elif defined(__rtems__)
 conditional should be true for vxWorks as well, but you'll have to find
 a vxWorks guru to verify that.
 
 -- 
 Eric Norum                                 eric.norum@usask.ca
 Department of Electrical Engineering       Phone: (306) 966-5394
 University of Saskatchewan                 FAX:   (306) 966-5407
 Saskatoon, Canada.