public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63672] xbegin/xend/xabort missing memory barriers Date: Thu, 20 Aug 2015 23:27:00 -0000 [thread overview] Message-ID: <bug-63672-4-sApTZDT6o9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63672-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63672 Peter Bergner <bergner at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bergner at gcc dot gnu.org --- Comment #1 from Peter Bergner <bergner at gcc dot gnu.org> --- Andi, did this bug ever get fixed? I ask, since we're hitting a similar issue on POWER with our __builtin_tbegin() builtin. I know we need a minimum of a memory barrier on our HTM builtins, but I also wonder whether a full optimization barrier is needed to stop even non loads and stores from being moved outside of the transaction body. The following shows a test case that seems to need a full optimization barrier: https://www.sourceware.org/ml/libc-alpha/2015-08/msg00880.html
next parent reply other threads:[~2015-08-20 23:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-63672-4@http.gcc.gnu.org/bugzilla/> 2015-08-20 23:27 ` bergner at gcc dot gnu.org [this message] 2024-02-16 6:32 ` 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-63672-4-sApTZDT6o9@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).