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][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: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org, Hans dot Boehm at hp dot com
Date: Mon, 10 Jul 2006 14:20:54 +0200
Subject: Re: [PATCH][RFC] Remove volatile from data members in libstdc++
References: <Pine.LNX.4.64.0607101250290.5439@nyjnma.fhfr.qr> <44B23303.8040204@suse.de> <Pine.LNX.4.64.0607101405000.5439@nyjnma.fhfr.qr>

Richard Guenther wrote:

Of course the only semantics that matter are those specified in the standard, and those are not useful in the context of locking or serialization.

To summarize, we have no idea why the (respected, would be Hans Boehm, I guess) author of that code decided to add the volatiles... I'd like to understand the issue a little better before going ahead...

I'm adding Hans Boehm in CC, maybe he want to comment... Thanks in advance, in case.

Paolo.

Follow-Ups:
- Re: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Benjamin Kosnik
- RE: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Boehm, Hans

References:
- [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]