Skip to content

Commit 3e72610

Browse files
authored
change total order to strict total order
1 parent 13ba96c commit 3e72610

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/basic.tex

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6201,11 +6201,11 @@
62016201

62026202
\pnum
62036203
All modifications to a particular atomic object $M$ occur in some
6204-
particular total order, called the \defn{modification order} of $M$.
6204+
particular strict total order, called the \defn{modification order} of $M$.
62056205
\begin{note}
62066206
There is a separate order for each
62076207
atomic object. There is no requirement that these can be combined into a single
6208-
total order for all objects. In general this will be impossible since different
6208+
strict total order for all objects. In general this will be impossible since different
62096209
threads can observe modifications to different objects in inconsistent orders.
62106210
\end{note}
62116211

@@ -6231,7 +6231,7 @@
62316231
The
62326232
specifications of the synchronization operations define when one reads the value
62336233
written by another. For atomic objects, the definition is clear. All operations
6234-
on a given mutex occur in a single total order. Each mutex acquisition ``reads
6234+
on a given mutex occur in a single strict total order. Each mutex acquisition ``reads
62356235
the value written'' by the last mutex release.
62366236
\end{note}
62376237

0 commit comments

Comments
 (0)