>From 5491d5d9aad320ba08b304bea3085cc0a02c9390 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Sat, 25 Mar 2017 17:46:04 +0900
Subject: [RFC PATCH 6/7] advsync: Properly use nbsp in initial values
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
advsync/memorybarriers.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
index da464fd..b6665b6 100644
--- a/advsync/memorybarriers.tex
+++ b/advsync/memorybarriers.tex
@@ -2544,7 +2544,7 @@ as shown in Figure~\ref{fig:advsync:Speculative Loads Cancelled by Barrier}.
``Transitivity'' is a deeply intuitive notion about ordering that is not
always provided by real computer systems. The following example
demonstrates transitivity with initial values of
-{\tt \{X = 0, Y = 0\}}:
+{\tt \{X~=~0, Y~=~0\}}:
\vspace{5pt}
\begin{minipage}[t]{\columnwidth}
@@ -2580,7 +2580,7 @@ also return~1.
However, transitivity is {\em not} guaranteed for read or write barriers.
For example, suppose that CPU~2's general barrier in the above example
is changed to a read barrier as shown below with the same initial values of
-{\tt \{X = 0, Y = 0\}}:
+{\tt \{X~=~0, Y~=~0\}}:
\vspace{5pt}
\begin{minipage}[t]{\columnwidth}
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
