[Bug libstdc++/65033] New: C++11 atomics: is_lock_free result does not always match the real lock-free property

2015-02-11 Thread bin.x.fan at oracle dot com
Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: bin.x.fan at oracle dot com Hi, The is_lock_free result for an object of type atomic, where s3_t is size=3, alignment=1 C style struct, does not always match the

[Bug libstdc++/65033] C++11 atomics: is_lock_free result does not always match the real lock-free property

2015-02-12 Thread bin.x.fan at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65033 --- Comment #5 from Bin Fan --- (In reply to Jason Merrill from comment #3) > (In reply to Bin Fan from comment #0) > > 2. g++ tries to make lock-free property per-type, but the libatomic.so > > implementation does not match. > > This. We alway

[Bug c/65083] New: Can not indirectly call some C11 atomic library functions

2015-02-16 Thread bin.x.fan at oracle dot com
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: bin.x.fan at oracle dot com C11 defines these as actual functions, not generic functions or macros: atomic_thread_fence atomic_signal_fence atomic_flag_test_and_set

[Bug libstdc++/66842] New: libatomic uses multiple locks for locked atomics

2015-07-11 Thread bin.x.fan at oracle dot com
: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: bin.x.fan at oracle dot com Target Milestone: --- Hi GCC folks, I'm opening this bug to report an issue that may or may not be a real bug. I notice that GCC libatomic uses multiple locks for a locked atomic o

[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 --- 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 because you're not even u

[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 changed: What|Removed |Added Component|c |c++ --- Comment #4 from Bin Fan --- Since I d

[Bug libstdc++/65033] C++11 atomics: is_lock_free result does not always match the real lock-free property

2015-07-16 Thread bin.x.fan at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65033 --- Comment #9 from Bin Fan --- I verified this bug is fixed in 5.1.0. However, it is only fixed in g++, so now in 5.1.0, gcc and g++ reports different result: -bash-4.1$ cat is_lock_free.c #include #include #define N 10 typedef struct { cha

[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 --- (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 best of > ideas -- things th