Skip to contentSkip to conversation

future/htm: Fix typo (missing '\' of \IXalt)

PATCH New Akira Yokosawa 2 participants 3 messages Jul 2, 2021 – Jul 4, 2021

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 future/htm: Fix typo (missing '\' of \IXalt)

Fixes de25a117a9c6 ("index: Add index and acronym tags, take one")

---
Hi Paul,

I fat-fingered this one in the big patch.
I'm thinking of adding some rules in the check script to catch this sort of typo.

Thanks, Akira
--

 future/htm.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
future/htm.tex +1 -1
index dc67ba23..7bff0f99 100644
@@ -252,7 +252,7 @@ write~\cite{RaviRajwar2012TSX}.
 schemes~\cite{CScottAnanian2006,KevinEMoore2006}
 use DRAM as an extremely large victim cache, but integrating such schemes
 into a production-quality
-IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved
+\IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved
 problem.
 In addition, use of DRAM as a victim cache may have unfortunate
 performance and energy-efficiency consequences, particularly
Signature · 1 line
2.17.1
#1 lore raw

PATCH v2 1/1 future/htm, summary: Fix typos (missing '\' in indexing macros)

Fixes b97d9921b0fd ("acronym: future/htm: Tag TM, HTM, STM, and RCU via acronym dictionary")
Fixes de25a117a9c6 ("index: Add index and acronym tags, take one")

---
Hi again,

Quoted 2 lines · I said:

I'm thinking of adding some rules in the check script to catch this sort of typo.

, and a tentative script caught two other typos.

This v2 patch fixes three typos at once.

Updated check script will be posted later along with other punctuation convention fixes.

Thanks, Akira
--

 future/htm.tex | 4 ++--
 summary.tex    | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
future/htm.tex +2 -2
index dc67ba23..7458f436 100644
@@ -150,7 +150,7 @@ HTM is therefore a very real possibility for large non-partitionable
 data structures, at least assuming relatively small updates.
 
 \QuickQuiz{
-	Why are relatively small updates important to IXacr{htm} performance
+	Why are relatively small updates important to \IXacr{htm} performance
 	and scalability?
 }\QuickQuizAnswer{
 	The larger the updates, the greater the probability of conflict,
@@ -252,7 +252,7 @@ write~\cite{RaviRajwar2012TSX}.
 schemes~\cite{CScottAnanian2006,KevinEMoore2006}
 use DRAM as an extremely large victim cache, but integrating such schemes
 into a production-quality
-IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved
+\IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved
 problem.
 In addition, use of DRAM as a victim cache may have unfortunate
 performance and energy-efficiency consequences, particularly
summary.tex +1 -1
index 63187998..2ed43920 100644
@@ -86,7 +86,7 @@ And that goes at least double for concurrent code.
 where combining concurrency mechanisms with each other or with other
 design tricks can greatly ease parallel programmers' lives.
 \Cref{sec:advsync:Advanced Synchronization} looked at advanced
-synchronization methods, including lockless programming, IXacrl{nbs},
+synchronization methods, including lockless programming, \IXacrl{nbs},
 and parallel real-time computing.
 \Cref{chp:Advanced Synchronization: Memory Ordering} dug into the
 critically important topic of memory ordering, presenting techniques
Signature · 1 line
2.17.1
#2 lore raw

Re: [PATCH -perfbook v2] future/htm, summary: Fix typos (missing '\' in indexing macros)

Quoted 11 lines · Akira Yokosawa
Fixes b97d9921b0fd ("acronym: future/htm: Tag TM, HTM, STM, and RCU via acronym dictionary")
Fixes de25a117a9c6 ("index: Add index and acronym tags, take one")

---
Hi again,

Quoted 2 lines · I said:

I'm thinking of adding some rules in the check script to catch this sort of typo.

Quoted 6 lines

, and a tentative script caught two other typos.

This v2 patch fixes three typos at once.

Updated check script will be posted later along with other punctuation convention fixes.

Queued and pushed, thank you!

Thanx, Paul

Quoted 45 lines

Thanks, Akira
--

 future/htm.tex | 4 ++--
 summary.tex    | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
future/htm.tex +2 -2
index dc67ba23..7458f436 100644
@@ -150,7 +150,7 @@ HTM is therefore a very real possibility for large non-partitionable
 data structures, at least assuming relatively small updates.
 
 \QuickQuiz{
-	Why are relatively small updates important to IXacr{htm} performance
+	Why are relatively small updates important to \IXacr{htm} performance
 	and scalability?
 }\QuickQuizAnswer{
 	The larger the updates, the greater the probability of conflict,
@@ -252,7 +252,7 @@ write~\cite{RaviRajwar2012TSX}.
 schemes~\cite{CScottAnanian2006,KevinEMoore2006}
 use DRAM as an extremely large victim cache, but integrating such schemes
 into a production-quality
-IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved
+\IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved
 problem.
 In addition, use of DRAM as a victim cache may have unfortunate
 performance and energy-efficiency consequences, particularly
summary.tex +1 -1
index 63187998..2ed43920 100644
@@ -86,7 +86,7 @@ And that goes at least double for concurrent code.
 where combining concurrency mechanisms with each other or with other
 design tricks can greatly ease parallel programmers' lives.
 \Cref{sec:advsync:Advanced Synchronization} looked at advanced
-synchronization methods, including lockless programming, IXacrl{nbs},
+synchronization methods, including lockless programming, \IXacrl{nbs},
 and parallel real-time computing.
 \Cref{chp:Advanced Synchronization: Memory Ordering} dug into the
 critically important topic of memory ordering, presenting techniques
Signature · 1 line
2.17.1