Fix typos in memorder.tex.
Signed-off-by: Junchang Wang <junchangwang@xxxxxxxxx>
---
memorder/memorder.tex | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index 8e11e92..a478f60 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -1364,7 +1364,7 @@ The head pointer is \co{x1}, which initially
references the \co{int} variable \co{y} (line~5), which is in turn
initialized to the value $1$ (line~4).
\co{P0()} updates head pointer \co{x1} to reference \co{x0} (line~12),
-but only afer initializing it to $2$ (line~10) and forcing ordering
+but only after initializing it to $2$ (line~10) and forcing ordering
(line~11).
\co{P1()} picks up the head pointer \co{x1} (line~21), and then loads
the referenced value (line~22).
@@ -2294,9 +2294,9 @@ These ordering constraints are depicted graphically in
Figure~\ref{fig:memorder:Cumulativity}.
Note also that cumulativity is not limited to a single step back in time.
If there was another load from \co{x} or store to \co{x} from any thread
-that came before the store on line~13, that prior load or store would also
-be ordered before the store on line~32, though only if both \co{r1} and
-\co{r2} both end up containing the address of \co{x}.
+that came before the store on line~8, that prior load or store would also
+be ordered before the store on line~16, though only if both \co{r1} and
+\co{r3} both end up containing the address of \co{x}.
In short, use of cumulative ordering operations can suppress
non-multicopy-atomic behaviors in some situations.
--
2.7.4
