K 10
svn:author
V 7
attilio
K 8
svn:date
V 27
2009-10-12T15:56:27.686285Z
K 7
svn:log
V 193
MFC r1979643:
When releasing a read/shared lock we need to use a write memory barrier
in order to avoid, on architectures which doesn't have strong ordered
writes, CPU instructions reordering.

END