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: Benjamin Kosnik <bkoz at redhat dot com>
To: Paolo Carlini <pcarlini at suse dot de>
Cc: rguenther at suse dot de, 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 16:20:00 -0500
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> <44B24626.80803@suse.de>

> 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 don't have a problem with this patch, as long as it is sufficiently
tested. 

I suspect that some of this is just the accumulation of patches over
the years. Some of this may be to fix various compiler behavior, to
avoid warnings, or to coax cetain output (and may not be relevant now).

-benjamin

Follow-Ups:
- Re: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Paolo Carlini

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
- Re: [PATCH][RFC] Remove volatile from data members in libstdc++
  - From: Paolo Carlini

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