Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2048)

Issue 6428056: [google-4.6]Backport r183875 to fix incorrect increment/decrement of atomic pointers

Can't Edit
Can't Publish+Mail
Start Review
Created:
11 years, 9 months ago by jingyu
Modified:
11 years, 9 months ago
CC:
gcc-patches_gcc.gnu.org
Base URL:
svn+ssh://gcc.gnu.org/svn/gcc/branches/google/gcc-4_6/libstdc++-v3/
Visibility:
Public.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+169 lines, -8 lines) Patch
M include/bits/atomic_0.h View 3 chunks +4 lines, -4 lines 0 comments Download
M include/bits/atomic_2.h View 1 chunk +4 lines, -4 lines 0 comments Download
A testsuite/29_atomics/atomic/operators/51811.cc View 1 chunk +90 lines, -0 lines 0 comments Download
A testsuite/29_atomics/atomic/operators/pointer_partial_void.cc View 1 chunk +71 lines, -0 lines 0 comments Download

Messages

Total messages: 4
jingyu
Backport r183875 from trunk and gcc-4.7 to fix PR51811 ([C++0x] Incorrect increment/decrement of atomic pointers). ...
11 years, 9 months ago (2012-07-19 22:11:34 UTC) #1
dougkwan
This seems to be different from r183875. Are the parts chaing is_look_free() in r183875 necessary? ...
11 years, 9 months ago (2012-07-19 22:29:32 UTC) #2
jingyu
It is not a straightforward backport. <atomic> has changed a lot in gcc-4.7. is_lock_free() body ...
11 years, 9 months ago (2012-07-19 22:48:14 UTC) #3
dougkwan
11 years, 9 months ago (2012-07-19 23:55:07 UTC) #4
LGTM.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b