This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/84522] GCC does not generate cmpxchg16b when mcx16 is used
- From: "nruslan_devel at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 22 Feb 2018 20:51:11 +0000
- Subject: [Bug target/84522] GCC does not generate cmpxchg16b when mcx16 is used
- Auto-submitted: auto-generated
- References: <bug-84522-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84522
--- Comment #3 from Ruslan Nikolaev <nruslan_devel at yahoo dot com> ---
(In reply to Ruslan Nikolaev from comment #2)
> Yes, but not having atomic_load is far less an issue. Oftentimes, algorithms
> that use 128-bit can simply use compare_and_exchange only (at least for
> x86-64).
In other words, can atomic_load be redirected to libatomic while
compare_exchange still be generated directly (if -mcx16 is specified)?