public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/39677] AMD Opteron E needs workaround for lock erratum Date: Mon, 19 Jul 2021 18:28:54 +0000 [thread overview] Message-ID: <bug-39677-4-swubVeIldO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-39677-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39677 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So reading https://www.amd.com/system/files/TechDocs/25759.pdf and errata #147, the errata only occurs if lock is not there: The erratum will not occur if there is a LOCK prefix on the read-modify-write instruction. And GCC never emits a cmpxchg without a lock prefix so there is nothing to be done.
next parent reply other threads:[~2021-07-19 18:28 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-39677-4@http.gcc.gnu.org/bugzilla/> 2021-07-19 18:28 ` pinskia at gcc dot gnu.org [this message] 2009-04-07 13:36 [Bug middle-end/39677] New: " bonzini at gnu dot org 2009-10-13 1:07 ` [Bug target/39677] " rth at gcc dot gnu dot org 2009-12-07 16:12 ` rth at gcc dot gnu dot 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-39677-4-swubVeIldO@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).