public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ozabluda at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/54786] Missing fence in std::atomic<T>::store() triggers wrong reordering.
Date: Tue, 02 Oct 2012 22:04:00 -0000	[thread overview]
Message-ID: <bug-54786-4-rEPLH3mRvR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54786-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54786

--- Comment #3 from Oleg Zabluda <ozabluda at gmail dot com> 2012-10-02 22:04:37 UTC ---
I can confirm that it is fixed in 4.7.0, after the move to __atomic builtins,
at least on x86_64. It would be nice to have it fixed in currently hypothetical
4.6.4, especially for those whose distro is stuck on 4.6. But at least it's
documented now and users can act accordingly. For example add
__sync_syncronise() or asm volatile ("":::"memory") before atomic::store().


  parent reply	other threads:[~2012-10-02 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 20:33 [Bug libstdc++/54786] New: " ozabluda at gmail dot com
2012-10-02 20:37 ` [Bug libstdc++/54786] " pinskia at gcc dot gnu.org
2012-10-02 20:39 ` pinskia at gcc dot gnu.org
2012-10-02 22:04 ` ozabluda at gmail dot com [this message]
2012-10-03  0:56 ` 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-54786-4-rEPLH3mRvR@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: link
Be 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).