public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/54172] [4.7/4.8 Regression] __cxa_guard_acquire thread-safety issue
Date: Thu, 06 Sep 2012 20:32:00 -0000	[thread overview]
Message-ID: <bug-54172-4-Yt7v4NU0uP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54172-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2012-09-06 20:31:13 UTC ---
Author: bkoz
Date: Thu Sep  6 20:31:08 2012
New Revision: 191042

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=191042
Log:
2012-09-06  Thiago Macieira  <thiago.macieira@intel.com>

    PR libstdc++/54172
        * libsupc++/guard.cc (__cxa_guard_acquire): Exit the loop earlier if
        we detect that another thread has had success. Don't compare_exchange
        from a finished state back to a waiting state. Comment.


Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/libsupc++/guard.cc


  parent reply	other threads:[~2012-09-06 20:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04 11:37 [Bug libstdc++/54172] New: [4.7 " thiago at kde dot org
2012-08-04 17:31 ` [Bug libstdc++/54172] [4.7/4.8 " rguenth at gcc dot gnu.org
2012-08-05 19:36 ` redi at gcc dot gnu.org
2012-08-10 15:07 ` jakub at gcc dot gnu.org
2012-08-30  2:40 ` foom at fuhm dot net
2012-08-30  7:53 ` thiago at kde dot org
2012-08-30  8:21 ` jakub at gcc dot gnu.org
2012-08-30  9:57 ` redi at gcc dot gnu.org
2012-09-01  8:27 ` thiago at kde dot org
2012-09-04 17:20 ` rth at gcc dot gnu.org
2012-09-04 17:48 ` thiago at kde dot org
2012-09-05 16:23 ` paolo.carlini at oracle dot com
2012-09-06 18:54 ` rth at gcc dot gnu.org
2012-09-06 20:32 ` bkoz at gcc dot gnu.org [this message]
2012-09-07 10:24 ` [Bug libstdc++/54172] [4.7 " rguenth at gcc dot gnu.org
2012-09-10  5:09 ` bkoz at gcc dot gnu.org
2012-09-10  5:10 ` bkoz at gcc dot gnu.org
2012-09-10  5:11 ` bkoz at gcc dot gnu.org
2012-09-11 15:24 ` jakub at gcc dot gnu.org
2012-09-11 15:25 ` jakub at gcc dot gnu.org
2012-09-11 15:26 ` jakub at gcc dot gnu.org
2012-09-20 10:20 ` jakub at gcc dot gnu.org
2012-09-26 18:41 ` bkoz 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-54172-4-Yt7v4NU0uP@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).