public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/46914] std::atomic<int*>::exchange(...) doesn't store correct value.
Date: Thu, 27 Jan 2011 15:52:00 -0000	[thread overview]
Message-ID: <bug-46914-4-gN06WbOAxc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46914-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-01-27 15:33:47 UTC ---
Ok. In any case we should not risk miscompiling stuff, better bailing out at
compile time. I see that in atomic_base.h the configure-time macros
_GLIBCXX_ATOMIC_BUILTINS_* are used and I se no uses of the
__GCC_HAVE_SYNC_COMPARE_AND_SWAP_* macros, the only one sensitive to the
command line switches. But apparently the PR is about compiling *without* any
special command line switch affecting the availability of the builtins, thus I
don't see how things could possibly go wrong. Something also to keep in mind is
that [GLIBCXX_ENABLE_ATOMIC_BUILTINS] in acinclude.m4 changed recently: I don't
think we want to go through big efforts fixing this issue affecting only C++0x
facilities in case it shows up only on 4.4.x, say, and it's fixed in mainline.
I'll also try to run further tests in mainline, multilib too.


  parent reply	other threads:[~2011-01-27 15:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 19:59 [Bug libstdc++/46914] New: " frtsang at hotmail dot com
2010-12-12 20:15 ` [Bug libstdc++/46914] " frtsang at hotmail dot com
2010-12-12 20:51 ` paolo.carlini at oracle dot com
2011-01-27 14:48 ` paolo.carlini at oracle dot com
2011-01-27 14:57 ` redi at gcc dot gnu.org
2011-01-27 15:17 ` paolo.carlini at oracle dot com
2011-01-27 15:18 ` redi at gcc dot gnu.org
2011-01-27 15:52 ` paolo.carlini at oracle dot com [this message]
2011-01-27 15:57 ` paolo.carlini at oracle dot com
2011-01-27 16:11 ` paolo.carlini at oracle dot com
2011-01-28  8:48 ` frtsang at hotmail dot com
2011-01-28 10:11 ` paolo.carlini at oracle dot com
2011-01-28 10:56 ` paolo.carlini at oracle dot com
2011-02-01 17:30 ` paolo.carlini at oracle dot com
2011-02-01 17:39 ` paolo.carlini at oracle dot com
2011-02-01 19:40 ` paolo at gcc dot gnu.org
2011-02-01 19:42 ` paolo at gcc dot gnu.org
2011-02-01 19:43 ` paolo.carlini at oracle dot com
2011-02-02 18:33 ` dnovillo 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-46914-4-gN06WbOAxc@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).