Volatile in Wintun
lstipakov at gmail.com
Wed Aug 21 15:14:53 CEST 2019
we don't assume that volatile implies a memory
> barrier. We could probably switch to /volatile:iso.
Does it mean that hardware reordering like writes reordered after reads
on x86/amd64 and everything else on ARM are not considered to be a problem?
Should barriers generated by WaitForSingleObject / SetEvent be enough?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the WireGuard