public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107676] New: Nonsensical docs for -mrelax-cmpxchg-loop Date: Mon, 14 Nov 2022 13:32:07 +0000 [thread overview] Message-ID: <bug-107676-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107676 Bug ID: 107676 Summary: Nonsensical docs for -mrelax-cmpxchg-loop Product: gcc Version: 12.2.1 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- Target: x86* g:4d281ff7ddd8f6365943c0a622107f92315bb8a6 added: +@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. 1) "cachline" is a typo 2) "when" ... when what? 3) What does "atomic logic fetch builtins" mean? 4) "generates" should be "generate" 5) Is a "cmpxchg loop" the same as a "compare and swap loop"? Can we use the same term consistently?
next reply other threads:[~2022-11-14 13:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-14 13:32 redi at gcc dot gnu.org [this message] 2022-11-14 13:57 ` [Bug target/107676] " redi at gcc dot gnu.org 2022-11-14 14:04 ` redi at gcc dot gnu.org 2022-11-14 17:16 ` pinskia at gcc dot gnu.org 2022-11-14 17:21 ` redi at gcc dot gnu.org 2022-11-14 17:26 ` pinskia at gcc dot gnu.org 2022-11-15 3:36 ` wwwhhhyyy333 at gmail dot com 2022-11-16 13:42 ` cvs-commit at gcc dot gnu.org 2022-11-16 13:43 ` amonakov at gcc dot gnu.org 2022-11-28 22:23 ` pinskia at gcc dot gnu.org
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=bug-107676-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).