A barrier name is not a complete specification. Ask which operations it orders, its shareability domain (the set of agents the ordering applies to), and what completion event it requires. Work these lessons after the SC/TSO examples, keeping per-location coherence separate from architecture and language contracts.
Lesson | After it you can... |
|---|---|
Order operations without requiring clean cache lines. | |
Identify which release the acquire must read from. | |
Preserve indivisibility as exclusive permission moves. | |
Name exactly what each observed completion establishes. |
Suggested order: fence scope, publication, atomic update, then completion evidence.
No. Ordering and cache cleaning have different contracts. A coherent dirty cache can remain the authoritative source after an ordering requirement has been satisfied.