maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Documentation for the new msasm flag, which is no 

worse than the rest of the asm documentation.

llvm-svn: 84037
This commit is contained in:
Dale Johannesen 2009-10-13 21:56:55 +00:00
parent 1fdbe1152d
commit 63c94fe1e2
1 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
llvm/docs/LangRef.html
View File

@ -2338,8 +2338,10 @@ has undefined behavior.</p>
to <a href="#moduleasm"> Module-Level Inline Assembly</a>) through the use of to <a href="#moduleasm"> Module-Level Inline Assembly</a>) through the use of
a special value. This value represents the inline assembler as a string a special value. This value represents the inline assembler as a string
(containing the instructions to emit), a list of operand constraints (stored (containing the instructions to emit), a list of operand constraints (stored
as a string), and a flag that indicates whether or not the inline asm as a string), a flag that indicates whether or not the inline asm
expression has side effects. An example inline assembler expression is:</p> expression has side effects, and a flag indicating whether the asm came
originally from an asm block. An example inline assembler
expression is:</p>
<div class="doc_code"> <div class="doc_code">
<pre> <pre>
@ -2367,6 +2369,18 @@ call void asm sideeffect "eieio", ""()
</pre> </pre>
</div> </div>
<p>Inline asms derived from asm blocks are similarly marked with the
'<tt>msasm</tt>' keyword:</p>
<div class="doc_code">
<pre>
call void asm msasm "eieio", ""()
</pre>
</div>
<p>If both keywords appear the '<tt>sideeffect</tt>' keyword must come
first.</p>
<p>TODO: The format of the asm and constraints string still need to be <p>TODO: The format of the asm and constraints string still need to be
documented here. Constraints on what can be done (e.g. duplication, moving, documented here. Constraints on what can be done (e.g. duplication, moving,
etc need to be documented). This is probably best done by reference to etc need to be documented). This is probably best done by reference to