|
1572 | 1572 | \begin{itemdescr} |
1573 | 1573 | \pnum |
1574 | 1574 | Let $P(\tcode{x}, \tcode{y})$ be |
1575 | | -an unspecified total ordering over \tcode{thread::id} |
| 1575 | +an unspecified strict total ordering over \tcode{thread::id} |
1576 | 1576 | as described in \ref{alg.sorting}. |
1577 | 1577 |
|
1578 | 1578 | \pnum |
|
2858 | 2858 | \end{itemize} |
2859 | 2859 |
|
2860 | 2860 | \pnum |
2861 | | -There is a single total order $S$ |
| 2861 | +There is a single strict total order $S$ |
2862 | 2862 | on all \tcode{memory_order::seq_cst} operations, including fences, |
2863 | 2863 | that satisfies the following constraints. |
2864 | 2864 | First, if $A$ and $B$ are |
|
6550 | 6550 | The implementation provides lock and unlock operations, as described below. |
6551 | 6551 | For purposes of determining the existence of a data race, these behave as |
6552 | 6552 | atomic operations\iref{intro.multithread}. The lock and unlock operations on |
6553 | | -a single mutex appears to occur in a single total order. |
| 6553 | +a single mutex appears to occur in a single strict total order. |
6554 | 6554 | \begin{note} |
6555 | 6555 | This |
6556 | 6556 | can be viewed as the modification order\iref{intro.multithread} of the |
|
8645 | 8645 |
|
8646 | 8646 | \pnum |
8647 | 8647 | \sync |
8648 | | -For any given \tcode{once_flag}: all active executions occur in a total |
| 8648 | +For any given \tcode{once_flag}: all active executions occur in a strict total |
8649 | 8649 | order; completion of an active execution synchronizes with\iref{intro.multithread} |
8650 | | -the start of the next one in this total order; and the returning execution |
| 8650 | +the start of the next one in this strict total order; and the returning execution |
8651 | 8651 | synchronizes with the return from all passive executions. |
8652 | 8652 |
|
8653 | 8653 | \pnum |
|
8718 | 8718 | \pnum |
8719 | 8719 | The implementation behaves as if all executions of \tcode{notify_one}, \tcode{notify_all}, and each |
8720 | 8720 | part of the \tcode{wait}, \tcode{wait_for}, and \tcode{wait_until} executions are |
8721 | | -executed in a single unspecified total order consistent with the ``happens before'' order. |
| 8721 | +executed in a single unspecified strict total order consistent with the ``happens before'' order. |
8722 | 8722 |
|
8723 | 8723 | \pnum |
8724 | 8724 | Condition variable construction and destruction need not be synchronized. |
|
0 commit comments