On Fri, 4 Dec 2009, Phil Endecott wrote:
Helge Bahmann wrote:
If this is always an "emulated" CAS
It could be an ll/sc sequence on systems that have those instructions. I don't think that counts as "emulated" in this sense, so memory barriers are needed - right?
ah, I didn't think it would be used at all if the platform could do ll/sc... you're right, in that case, you will definitely need the barriers
(BTW, why do you use leading __s ? I was under the impression that such identifiers were reserved.)
habit of mine to name really internal stuff that way, I can change it if it collides with boost coding style
I think that would be a good idea - "namespace detail" sufficiently identifies these things as being internal. While you're at it, I suggest adding some license/copyright headers.
okay, as Peter Dimov pointed out it collides with stdlib, so will change that Helge