[Bug c++/66842] libatomic uses multiple locks for locked atomics

2015-08-03 Thread rth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66842 --- Comment #7 from Richard Henderson rth at gcc dot gnu.org --- (In reply to Bin Fan from comment #6) Could you clarify what does aliased pages mean? Do you mean the same object is mapped into two or more different processes with different

[Bug c++/66842] libatomic uses multiple locks for locked atomics

2015-07-31 Thread bin.x.fan at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66842 --- Comment #6 from Bin Fan bin.x.fan at oracle dot com --- (In reply to Richard Henderson from comment #5) When libatomic was first written, it wasn't clear what the restrictions from the various languages would be, nor even if that was the

[Bug c++/66842] libatomic uses multiple locks for locked atomics

2015-07-30 Thread rth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66842 Richard Henderson rth at gcc dot gnu.org changed: What|Removed |Added CC||rth at gcc dot

[Bug c++/66842] libatomic uses multiple locks for locked atomics

2015-07-15 Thread bin.x.fan at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66842 Bin Fan bin.x.fan at oracle dot com changed: What|Removed |Added Component|c |c++ --- Comment #4

[Bug c/66842] libatomic uses multiple locks for locked atomics

2015-07-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66842 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Component|libstdc++ |c --- Comment

[Bug c/66842] libatomic uses multiple locks for locked atomics

2015-07-13 Thread bin.x.fan at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66842 --- Comment #2 from Bin Fan bin.x.fan at oracle dot com --- I couldn't find a category for libatomic, and my understand is that C and C++ share libatomic library. (In reply to Jonathan Wakely from comment #1) This obviously isn't a libstdc++

[Bug c/66842] libatomic uses multiple locks for locked atomics

2015-07-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66842 --- Comment #3 from Jonathan Wakely redi at gcc dot gnu.org --- Yes, so either C or C++ might be appropriate, but not libstdc++.