This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/59767] __atomic_load_n with __ATOMIC_SEQ_CST should result in a memory barrier
- From: "amacleod at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 06 Jul 2015 16:16:00 +0000
- Subject: [Bug target/59767] __atomic_load_n with __ATOMIC_SEQ_CST should result in a memory barrier
- Auto-submitted: auto-generated
- References: <bug-59767-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59767
--- Comment #4 from Andrew Macleod <amacleod at redhat dot com> ---
I'm not sure where the problem is. We interacted quite a bit as the model was
being developed. As I recall, it started with the standard, but they
strengthened some of the problem spots for a complete testable model.
To the best of my knowledge, this is the most efficient implementation that we
*know* to be safe, and that is why we implement it.