Skip to content

[atomics.order] Memory operations should be definitions #6567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/threads.tex
Original file line number Diff line number Diff line change
Expand Up @@ -2483,10 +2483,10 @@
\item \tcode{memory_order::relaxed}: no operation orders memory.

\item \tcode{memory_order::release}, \tcode{memory_order::acq_rel}, and
\tcode{memory_order::seq_cst}: a store operation performs a release operation on the
\tcode{memory_order::seq_cst}: a store operation performs a \defn{release operation} on the
affected memory location.

\item \tcode{memory_order::consume}: a load operation performs a consume operation on the
\item \tcode{memory_order::consume}: a load operation performs a \defn{consume operation} on the
affected memory location.
\begin{note}
Prefer \tcode{memory_order::acquire}, which provides stronger guarantees
Expand All @@ -2496,7 +2496,7 @@
\end{note}

\item \tcode{memory_order::acquire}, \tcode{memory_order::acq_rel}, and
\tcode{memory_order::seq_cst}: a load operation performs an acquire operation on the
\tcode{memory_order::seq_cst}: a load operation performs an \defn{acquire operation} on the
affected memory location.
\end{itemize}

Expand Down