public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexander Monakov <amonakov@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-4094] doc: fix description of -mrelax-cmpxchg-loop [PR 107676] Date: Wed, 16 Nov 2022 13:42:03 +0000 (GMT) [thread overview] Message-ID: <20221116134203.5D4A6395A41E@sourceware.org> (raw) https://gcc.gnu.org/g:85966f0d20baf50a767ac1110f537395441604a9 commit r13-4094-g85966f0d20baf50a767ac1110f537395441604a9 Author: Alexander Monakov <amonakov@ispras.ru> Date: Wed Nov 16 16:33:11 2022 +0300 doc: fix description of -mrelax-cmpxchg-loop [PR 107676] gcc/ChangeLog: PR target/107676 * doc/invoke.texi (-mrelax-cmpxchg-loop): Reword description. Diff: --- gcc/doc/invoke.texi | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index cbfe1102bd2..96f0b6d08bd 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -33561,10 +33561,11 @@ registers. @item -mrelax-cmpxchg-loop @opindex mrelax-cmpxchg-loop -Relax cmpxchg loop by emitting an early load and compare before cmpxchg, -execute pause if load value is not expected. This reduces excessive -cachline bouncing when and works for all atomic logic fetch builtins -that generates compare and swap loop. +When emitting a compare-and-swap loop for @ref{__sync Builtins} +and @ref{__atomic Builtins} lacking a native instruction, optimize +for the highly contended case by issuing an atomic load before the +@code{CMPXCHG} instruction, and using the @code{PAUSE} instruction +to save CPU power when restarting the loop. @item -mindirect-branch=@var{choice} @opindex mindirect-branch
reply other threads:[~2022-11-16 13:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20221116134203.5D4A6395A41E@sourceware.org \ --to=amonakov@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).