This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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][RFC] Remove volatile from data members in libstdc++

From: Paolo Carlini <pcarlini at suse dot de>
To: Richard Guenther <rguenther at suse dot de>
Cc: "Boehm, Hans" <hans dot boehm at hp dot com>, gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
Date: Wed, 12 Jul 2006 14:33:11 +0200
Subject: Re: [PATCH][RFC] Remove volatile from data members in libstdc++
References: <65953E8166311641A685BDF71D865826C1DD06@cacexc12.americas.cpqcorp.net> <Pine.LNX.4.64.0607121152540.5439@nyjnma.fhfr.qr> <Pine.LNX.4.64.0607121223420.5439@nyjnma.fhfr.qr> <44B4E6BD.4000809@suse.de> <Pine.LNX.4.64.0607121427380.5439@nyjnma.fhfr.qr>

Richard Guenther wrote:

Indeed. The volatiles can be removed on the mainline though.

Honestly, I didn't follow the whole thread: I trust you and Hans, about that. Any (ABI-safe) change to rope endorsed by Hans is preapproved.

I did. But rope testsuite coverage is not exactly interesting ;)

I told you... ;) But at least we have got thread-7-rope, or something like that.

Paolo.

References:
- RE: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Boehm, Hans
- RE: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Richard Guenther
- RE: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Richard Guenther
- Re: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Paolo Carlini
- Re: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Richard Guenther

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