public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/48076] Unsafe double checked locking in __emutls_get_address
Date: Thu, 29 Nov 2012 21:11:00 -0000	[thread overview]
Message-ID: <bug-48076-4-kYY9a5TVQI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48076-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #10 from Richard Henderson <rth at gcc dot gnu.org> 2012-11-29 21:11:05 UTC ---
Author: rth
Date: Thu Nov 29 21:11:00 2012
New Revision: 193959

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193959
Log:
PR libgcc/48076
        * emutls.c (__emutls_get_address): Add memory barrier before
        referencing emutls_key.

Modified:
    branches/gcc-4_6-branch/gcc/ChangeLog
    branches/gcc-4_6-branch/gcc/emutls.c


  parent reply	other threads:[~2012-11-29 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 16:01 [Bug middle-end/48076] New: " eugeni.stepanov at gmail dot com
2011-03-11 16:34 ` [Bug middle-end/48076] " pinskia at gcc dot gnu.org
2012-11-27 18:01 ` [Bug sanitizer/48076] " rth at gcc dot gnu.org
2012-11-27 18:18 ` rth at gcc dot gnu.org
2012-11-27 22:05 ` rth at gcc dot gnu.org
2012-11-28  3:52 ` dvyukov at google dot com
2012-11-28  3:57 ` dvyukov at google dot com
2012-11-28 14:30 ` torvald at gcc dot gnu.org
2012-11-28 21:01 ` [Bug libgcc/48076] " rth at gcc dot gnu.org
2012-11-29 21:06 ` rth at gcc dot gnu.org
2012-11-29 21:11 ` rth at gcc dot gnu.org [this message]
2012-11-29 21:14 ` rth 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-48076-4-kYY9a5TVQI@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).