diff options
author | Alexander Monakov <amonakov@ispras.ru> | 2017-09-01 17:08:42 +0300 |
---|---|---|
committer | Alexander Monakov <amonakov@gcc.gnu.org> | 2017-09-01 17:08:42 +0300 |
commit | 44acb9ba2b8ed7b588d5975773e591f477ef35c2 (patch) | |
tree | ba9e68e17af56e94b88d6f133936068ba9a8577e /gcc/doc | |
parent | 3ca3c6ef7110fb842cf8175a58d91d239c418bbe (diff) | |
download | gcc-44acb9ba2b8ed7b588d5975773e591f477ef35c2.zip gcc-44acb9ba2b8ed7b588d5975773e591f477ef35c2.tar.gz gcc-44acb9ba2b8ed7b588d5975773e591f477ef35c2.tar.bz2 |
retire mem_signal_fence pattern
* config/s390/s390.md (mem_signal_fence): Remove.
* doc/md.texi (mem_signal_fence): Remove.
* optabs.c (expand_mem_signal_fence): Remove uses of mem_signal_fence.
Update comments.
* target-insns.def (mem_signal_fence): Remove.
From-SVN: r251597
Diffstat (limited to 'gcc/doc')
-rw-r--r-- | gcc/doc/md.texi | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi index 64a137e..ed78df8 100644 --- a/gcc/doc/md.texi +++ b/gcc/doc/md.texi @@ -7059,19 +7059,6 @@ If this pattern is not defined, the compiler falls back to expanding the @code{memory_barrier} pattern, then to emitting @code{__sync_synchronize} library call, and finally to just placing a compiler memory barrier. -@cindex @code{mem_signal_fence@var{mode}} instruction pattern -@item @samp{mem_signal_fence@var{mode}} -This pattern emits code required to implement a signal fence with -memory model semantics. Operand 0 is the memory model to be used. - -This pattern should impact the compiler optimizers the same way that -mem_signal_fence does, but it does not need to issue any barrier -instructions. - -If this pattern is not specified, all memory models except -@code{__ATOMIC_RELAXED} will result in issuing a @code{sync_synchronize} -barrier pattern. - @cindex @code{get_thread_pointer@var{mode}} instruction pattern @cindex @code{set_thread_pointer@var{mode}} instruction pattern @item @samp{get_thread_pointer@var{mode}} |