public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/45025] Memory ordering issues with libgomp critical sections and __sync Date: Thu, 22 Jul 2010 07:59:00 -0000 [thread overview] Message-ID: <20100722075905.32092.qmail@sourceware.org> (raw) In-Reply-To: <bug-45025-6957@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from jakub at gcc dot gnu dot org 2010-07-22 07:59 ------- So, 1. is fixed. If __sync_*compare_and_swap on PowerPC doesn't act as full barrier, that would be a target bug, not libgomp bug. Unless separate __sync_*_acq/__sync_*_rel builtins are added, I'm afraid the only option for libgomp would be on the weakly ordered targets to use inline asm instead, which wouldn't be very pretty. -- jakub at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rth at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45025
next prev parent reply other threads:[~2010-07-22 7:59 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-21 18:43 [Bug libgomp/45025] New: " Hans dot Boehm at hp dot com 2010-07-21 22:39 ` [Bug libgomp/45025] " sje at cup dot hp dot com 2010-07-22 7:59 ` jakub at gcc dot gnu dot org [this message] 2010-07-22 18:03 ` Hans dot Boehm at hp dot com 2010-07-22 18:41 ` jason at gcc dot gnu dot org [not found] <bug-45025-4@http.gcc.gnu.org/bugzilla/> 2012-02-03 2:50 ` pinskia at gcc dot gnu.org 2024-04-09 1:36 ` 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=20100722075905.32092.qmail@sourceware.org \ --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).