This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/54004] __atomic_always_lock_free / __atomic_is_lock_free has a faulty implementation in which the target has no saying
- From: "hp at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 17 Jul 2012 21:03:43 +0000
- Subject: [Bug tree-optimization/54004] __atomic_always_lock_free / __atomic_is_lock_free has a faulty implementation in which the target has no saying
- Auto-submitted: auto-generated
- References: <bug-54004-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54004
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|__atomic_always_lock_free |__atomic_always_lock_free /
|has a fault implementation |__atomic_is_lock_free has a
|in which the target has no |faulty implementation in
|saying |which the target has no
| |saying
--- Comment #1 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-07-17 21:03:43 UTC ---
Changing the title to explicitly include __atomic_is_lock_free here (and to fix
a typo). Not exactly the same problem, but once the issue shared with
__atomic_always_lock_free is fixed, it'd be nice to expand through a MD
pattern, and not just emit a library call.