Editing Release consistency (section)

=== Weak ordering ([[Weak consistency]]) ===
Release consistency requires more from the programmers compared to weak ordering. They must label synchronization accesses as acquires or releases, not just as synchronization accesses. Similar to weak ordering, Release consistency allows the compiler to freely reorder loads and stores except that they cannot migrate upward past an acquire synchronization and cannot migrate downward past a release synchronization. However, the flexibility and performance advantage of Release consistency comes at the expense of requiring synchronization accesses to be properly identified and identified as acquires and releases. Unlike in weak ordering, synchronization accesses cannot be easily identified by instruction opcodes alone. Hence, the burden is on programmers’ shoulders to properly identify acquire and release synchronization accesses.<ref name=":0" /><ref>{{Cite book|title=Parallel Computer Architecture: A Hardware/Software Approach|last=Culler|first=David|last2=Gupta|first2=Anoop|last3=Singh|first3=Jaswinder|publisher=Morgan Kaufmann Publishers Inc.|year=1997|isbn=1558603433|pages=620–626}}</ref>