mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-01-27 14:34:58 +00:00
Silly HTML
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@40117 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
2067764e29
commit
1cff40819c
@ -5078,13 +5078,13 @@ declare void @llvm.memory.barrier( i1 <ll>, i1 <ls>, i1 <sl>,
|
||||
<p>
|
||||
The <tt>llvm.memory.barrier</tt> intrinsic requires four boolean arguments.
|
||||
Each argument enables a specific barrier as listed below.
|
||||
</p>
|
||||
<ul>
|
||||
<li><tt>ll</tt>: load-load barrier</li>
|
||||
<li><tt>ls</tt>: load-store barrier</li>
|
||||
<li><tt>sl</tt>: store-load barrier</li>
|
||||
<li><tt>ss</tt>: store-store barrier</li>
|
||||
</ul>
|
||||
</p>
|
||||
<h5>Semantics:</h5>
|
||||
<p>
|
||||
This intrinsic causes the system to enforce some ordering constraints upon
|
||||
@ -5094,6 +5094,7 @@ declare void @llvm.memory.barrier( i1 <ll>, i1 <ls>, i1 <sl>,
|
||||
(f.ex. load-load, or store-load), all of the first operations preceding the
|
||||
barrier will complete before any of the second operations succeeding the
|
||||
barrier begin. Specifically the semantics for each pairing is as follows:
|
||||
</p>
|
||||
<ul>
|
||||
<li><tt>ll</tt>: All loads before the barrier must complete before any load
|
||||
after the barrier begins.</li>
|
||||
@ -5104,6 +5105,7 @@ declare void @llvm.memory.barrier( i1 <ll>, i1 <ls>, i1 <sl>,
|
||||
<li><tt>sl</tt>: All stores before the barrier must complete before any
|
||||
load after the barrier begins.</li>
|
||||
</ul>
|
||||
<p>
|
||||
These semantics are applied with a logical "and" behavior when more than one
|
||||
is enabled in a single memory barrier intrinsic.
|
||||
</p>
|
||||
|
Loading…
x
Reference in New Issue
Block a user