This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH (libstdc++-v3 mainline): Re-enable i386/atomicity.h

From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
To: joel dot sherrill at OARcorp dot com
Cc: martin at v dot loewis dot de, libstdc++ at gcc dot gnu dot org
Date: Mon, 5 May 2003 17:42:58 -0500 (CDT)
Subject: Re: PATCH (libstdc++-v3 mainline): Re-enable i386/atomicity.h
References: <200304292202.h3TM2i96031935@latour.rsch.comm.mot.com> <m3y91nf4ec.fsf@mira.informatik.hu-berlin.de> <3EB668EE.A30BE7E6@OARcorp.com> <m3he89azei.fsf@mira.informatik.hu-berlin.de> <3EB6D159.ADB7F6A6@OARcorp.com>
Reply-to: rittle at labs dot mot dot com

In article <3EB6D159.ADB7F6A6@OARcorp.com>,
Joel Sherrill<joel.sherrill@OARcorp.com> writes:

> And technically 3.2.x gcc broke compatability with 3.2 for i386 target.
> From what I can tell from RTEMS user's bug reports, this crept in
> around 3.2.1 but was OK in 3.2.  This is a minor issue to me at this
> point.  I just want a functioning 3.3 for i386 targets. 

Sorry, I just don't know how that is possible.  We shipped a wrong
implementation of i386 atomics in every version of gcc from 3.0 until
3.2.3.

Follow-Ups:
- Re: PATCH (libstdc++-v3 mainline): Re-enable i386/atomicity.h
  - From: Joel Sherrill

References:
- Re: PATCH (libstdc++-v3 mainline): Re-enable i386/atomicity.h
  - From: Martin v. Löwis
- Re: PATCH (libstdc++-v3 mainline): Re-enable i386/atomicity.h
  - From: Joel Sherrill
- Re: PATCH (libstdc++-v3 mainline): Re-enable i386/atomicity.h
  - From: Martin v. Löwis
- Re: PATCH (libstdc++-v3 mainline): Re-enable i386/atomicity.h
  - From: Joel Sherrill

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]