public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jingyu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51811] [C++0x] Incorrect increment/decrement of atomic pointers
Date: Fri, 20 Jul 2012 17:28:00 -0000	[thread overview]
Message-ID: <bug-51811-4-URFTG0rhG2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51811-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jing Yu <jingyu at gcc dot gnu.org> 2012-07-20 17:28:09 UTC ---
Author: jingyu
Date: Fri Jul 20 17:27:57 2012
New Revision: 189724

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=189724
Log:
2012-07-19  Jing Yu  <jingyu@google.com>

    Backport r183875 to fix wrong atomic<_Tp*> add_fetch.
    PR libstdc++/51811, Google ref b/6702865
    * include/bits/atomic_0.h (atomic<_Tp*>): Fix offsets.
    * include/bits/atomic_2.h: Likewise.
    * testsuite/29_atomics/atomic/operators/51811.cc: New.
    * testsuite/29_atomics/atomic/operators/pointer_partial_void.cc: New.

Added:
   
branches/google/gcc-4_6/libstdc++-v3/testsuite/29_atomics/atomic/operators/51811.cc
   
branches/google/gcc-4_6/libstdc++-v3/testsuite/29_atomics/atomic/operators/pointer_partial_void.cc
Modified:
    branches/google/gcc-4_6/libstdc++-v3/ChangeLog.google-4_6
    branches/google/gcc-4_6/libstdc++-v3/include/bits/atomic_0.h
    branches/google/gcc-4_6/libstdc++-v3/include/bits/atomic_2.h


      parent reply	other threads:[~2012-07-20 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 14:22 [Bug libstdc++/51811] New: [C++0x] Incorrect incrementation/decrementation " t.schuele at web dot de
2012-02-03 19:41 ` [Bug libstdc++/51811] " bkoz at gcc dot gnu.org
2012-02-03 19:49 ` bkoz at gcc dot gnu.org
2012-02-15  3:02 ` bkoz at gcc dot gnu.org
2012-07-20 17:28 ` jingyu at gcc dot gnu.org [this message]

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-51811-4-URFTG0rhG2@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).