On 17-05-2011 19:58, Vlad Khorsun wrote: >> PS: There is a paper >> (http://www.aristeia.com/Papers/DDJ_Jul_Aug_2004_revised.pdf) from Scott >> Meyers and Andrei Alexandrescu showing even or volatile usage in base >> classes are wrong. Unfortunately it's down. > > With MSVC we are safe as we use "volatile" and compiler used read\write > memory > barriers (or acquire\release semantics) for access to volatile variables : > > http://msdn.microsoft.com/en-us/library/ms686355.aspx > > Can't said for other compilers (GCC at the first place). > Most usage of volatile to implement double-check locking pattern is in platform neutral code, hence wrong.
Adriano ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
