[llvm-dev] Memory scope proposal

[Tye, Tony via llvm-dev]

> Since the scope is “opaque” and target specific, can you elaborate what kind of generic optimization can be performed?

Some optimizations that are related to a single thread could be done without needing to know the actual memory scope. For example, an atomic acquire can restrict reordering memory operations after it, but allow reordering of memory operations (except another atomic acquire) before it, regardless of the memory scope.

Thanks,
-Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160823/be78b51c/attachment-0001.html>