toolsoftrade: Typo fix and context adjustment
PATCH 1/1 toolsoftrade: Typo fix and context adjustment
From 80b39e5d9acfec943c28d41077494be696d4ac60 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <[email protected]>
Date: Sun, 9 Apr 2017 18:54:40 +0900
Subject: [PATCH] toolsoftrade: Typo fix and context adjustment
There are three primitives introduced here now: barrier(), READ_ONCE(), and WRITE_ONCE().
Fixes 7945ae1a06c5 ("Further editing to Tools of Trade")
Signed-off-by Akira Yokosawa <[email protected]>
--- toolsoftrade/toolsoftrade.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
toolsoftrade/toolsoftrade.tex +2 -2
@@ -1247,8 +1247,8 @@ avoids optimizing away a given memory read, in which case the \co{READ_ONCE()} primitive may be used, as it was on line~17 of Figure~\ref{fig:toolsoftrade:Demonstration of Exclusive Locks}. Similarly, the \co{WRITE_ONCE()} primitive may be used to prevent the -compiler from optimizing a way a given memory write. -These last two primitives are not provided directly by gcc, +compiler from optimizing away a given memory write. +These last three primitives are not provided directly by gcc, but may be implemented straightforwardly as follows: \vspace{5pt}
Signature · 1 line
2.7.4
Quoted 10 lines · Akira Yokosawa
Quoted 1 line
From
80b39e5d9acfec943c28d41077494be696d4ac60Mon Sep 17 00:00:00 2001From: Akira Yokosawa <[email protected]>
Date: Sun, 9 Apr 2017 18:54:40 +0900
Subject: [PATCH] toolsoftrade: Typo fix and context adjustmentThere are three primitives introduced here now:
barrier(),READ_ONCE(), andWRITE_ONCE().Fixes 7945ae1a06c5 ("Further editing to Tools of Trade")Signed-off-by Akira Yokosawa <[email protected]>
Good catch, applied, thank you!
Thanx, Paul
Quoted 22 lines
--- toolsoftrade/toolsoftrade.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)toolsoftrade/toolsoftrade.tex +2
-2@@ -1247,8 +1247,8 @@ avoids optimizing away a given memory read, in which case the \co{READ_ONCE()} primitive may be used, as it was on line~17 of Figure~\ref{fig:toolsoftrade:Demonstration of Exclusive Locks}. Similarly, the \co{WRITE_ONCE()} primitive may be used to prevent the -compiler from optimizing a way a given memory write. -These last two primitives are not provided directly by gcc, +compiler from optimizing away a given memory write. +These last three primitives are not provided directly by gcc, but may be implemented straightforwardly as follows: \vspace{5pt}Signature · 1 line
2.7.4