6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-03-04 05:31:51 +00:00
Code Issues Projects Releases Wiki Activity

More cleanups. No content change.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@145522 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Bill Wendling 2011-11-30 21:52:43 +00:00
parent f6cc4c2d60
commit aee0f453c5
1 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/LangRef.html
View File

@ -2800,7 +2800,7 @@ second_end:
<div> <div>
<p>LLVM supports inline assembler expressions (as opposed <p>LLVM supports inline assembler expressions (as opposed
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), a flag that indicates whether or not the inline asm as a string), a flag that indicates whether or not the inline asm
@ -2842,23 +2842,27 @@ call void asm alignstack "eieio", ""()
<p>If both keywords appear the '<tt>sideeffect</tt>' keyword must come <p>If both keywords appear the '<tt>sideeffect</tt>' keyword must come
first.</p> 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
another document that covers inline asm from a holistic perspective.</p> another document that covers inline asm from a holistic perspective.</p>
-->
<!-- _______________________________________________________________________ -->
<h4> <h4>
<a name="inlineasm_md">Inline Asm Metadata</a> <a name="inlineasm_md">Inline Asm Metadata</a>
</h4> </h4>
<div> <div>
<p>The call instructions that wrap inline asm nodes may have a "!srcloc" MDNode <p>The call instructions that wrap inline asm nodes may have a
attached to it that contains a list of constant integers. If present, the "<tt>!srcloc</tt>" MDNode attached to it that contains a list of constant
code generator will use the integer as the location cookie value when report integers. If present, the code generator will use the integer as the
errors through the LLVMContext error reporting mechanisms. This allows a location cookie value when report errors through the <tt>LLVMContext</tt>
front-end to correlate backend errors that occur with inline asm back to the error reporting mechanisms. This allows a front-end to correlate backend
source code that produced it. For example:</p> errors that occur with inline asm back to the source code that produced it.
For example:</p>
<pre class="doc_code"> <pre class="doc_code">
call void asm sideeffect "something bad", ""()<b>, !srcloc !42</b> call void asm sideeffect "something bad", ""()<b>, !srcloc !42</b>
@ -2867,7 +2871,7 @@ call void asm sideeffect "something bad", ""()<b>, !srcloc !42</b>
</pre> </pre>
<p>It is up to the front-end to make sense of the magic numbers it places in the <p>It is up to the front-end to make sense of the magic numbers it places in the
IR. If the MDNode contains multiple constants, the code generator will use IR. If the MDNode contains multiple constants, the code generator will use
the one that corresponds to the line of the asm that the error occurs on.</p> the one that corresponds to the line of the asm that the error occurs on.</p>
</div> </div>