This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/80640] Missing memory side effect with __atomic_thread_fence (2)
- From: "amonakov at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 28 Aug 2017 10:59:18 +0000
- Subject: [Bug target/80640] Missing memory side effect with __atomic_thread_fence (2)
- Auto-submitted: auto-generated
- References: <bug-80640-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80640
--- Comment #8 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Author: amonakov
Date: Mon Aug 28 10:58:45 2017
New Revision: 251377
URL: https://gcc.gnu.org/viewcvs?rev=251377&root=gcc&view=rev
Log:
optabs: ensure mem_thread_fence is a compiler barrier
PR target/80640
* doc/md.texi (mem_thread_fence): Remove mention of mode. Rewrite.
* optabs.c (expand_mem_thread_fence): Emit a compiler barrier when
using targetm.gen_mem_thread_fence.
testsuite/
* gcc.dg/atomic/pr80640.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/atomic/pr80640.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/doc/md.texi
trunk/gcc/optabs.c
trunk/gcc/testsuite/ChangeLog