This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/54861] std::atomic_signal_fence(std::memory_order_seq_cst) issues unnecessary mfence
- From: "amacleod at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 09 Oct 2012 18:34:08 +0000
- Subject: [Bug libstdc++/54861] std::atomic_signal_fence(std::memory_order_seq_cst) issues unnecessary mfence
- Auto-submitted: auto-generated
- References: <bug-54861-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54861
Andrew Macleod <amacleod at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-10-09
AssignedTo|unassigned at gcc dot |amacleod at redhat dot com
|gnu.org |
Ever Confirmed|0 |1
--- Comment #1 from Andrew Macleod <amacleod at redhat dot com> 2012-10-09 18:34:08 UTC ---
Created attachment 28402
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28402
patch to resolve the problem
Just a typo in the header file where __atomic_thread_fence() built-in was being
called instead of the __atomic_signal_fence() built-in function.