7 Oct
2007
7 Oct
'07
6:19 p.m.
John Maddock wrote:
Secondly, I'm a bit confused why the barrier is *after* the read, shouldn't it be before? I'm not saying it should be, I just wondered :-)
The acquire semantics enforce that no load or store may be moved from behind to in front of the read, or the read be deferred until after a subsequent load or store accordingly. That's why the barrier has to be placed directly after the read. Timmo Stange