This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][RFC] Remove volatile from data members in libstdc++
- From: Richard Guenther <rguenther at suse dot de>
- To: Paolo Carlini <pcarlini at suse dot de>
- Cc: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Mon, 10 Jul 2006 14:08:40 +0200 (CEST)
- 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>
On Mon, 10 Jul 2006, Paolo Carlini wrote:
> Hi Richard,
>
> >This patch removes volatile qualifiers from data members in allocator
> >classes of libstdc++ and rope. As mentioned in previous discussion,
> >their use is wrong.
> >
> honestly I don't remember the details of that discussion and, well, in general
> there aren't so many stupid things in the original HP/SGI code (rope,
> pool_allocator). Maybe it's because of the slightly different semantics of
> volatile in GCC and in the original SGI compiler?!?
Searching I only found
http://gcc.gnu.org/ml/gcc-patches/2006-03/msg01008.html
and the followup
http://gcc.gnu.org/ml/gcc-patches/2006-03/msg01002.html
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.
Thanks,
Richard.
--
Richard Guenther <rguenther@suse.de>
Novell / SUSE Labs