Remove misleading note about AMOSWAP elision

The note implied that it's legal to elide silent stores.  This is not true
with respect to the consistency model.

1 files changed, 0 insertions, 6 deletions

diff --git a/src/a.tex b/src/a.tex
index 3b3ce9f..11bb4b7 100644
--- a/src/a.tex
+++ b/src/a.tex
@@ -405,12 +405,6 @@ the critical section before the lock relinquishment.
 We recommend the use of the AMO Swap idiom shown above for both lock
 acquire and release to simplify the implementation of speculative lock
 elision~\cite{Rajwar:2001:SLE}.
-
-At the risk of complicating the implementation of atomic operations,
-microarchitectures can elide the store within the acquire swap if the
-lock value matches the swap value, to avoid dirtying a cache line held
-in a shared or exclusive clean state.  The effect is similar to a
-test-and-test-and-set lock but with shorter code paths.
 \end{commentary}
 
 The instructions in the ``A'' extension can also be used to provide