RPCSX/llvm
1
0
Fork 0
mirror of https://github.com/RPCSX/llvm.git synced 2025-02-13 09:14:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Removed the interrupt_handler instrinsic section that I accidently added

Browse Source 
in my previous commits.  It's not implemented and is out of date.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@14410 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
John Criswell 2004-06-25 16:42:50 +00:00
parent 8411475105
commit f5076133a9
1 changed files with 0 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
docs/LangRef.html
View File

@ -2357,53 +2357,6 @@ ensures that accesses to memory mapped I/O registers occur in program order.
</div> </div>
<!-- _______________________________________________________________________ -->
<div class="doc_subsubsection">
<a name="i_interrupt_handler">'<tt>llvm.interrupt_handler</tt>' Intrinsic</a>
</div>
<div class="doc_text">
<h5>Syntax:</h5>
<pre>
call void (void)* %llvm.interrupt_handler (void)
</pre>
<h5>Overview:</h5>
<p>
The '<tt>llvm.interrupt_handler</tt>' intrinsic installs the specified function
as an interrupt handler for the specified interrupt.
</p>
<h5>Arguments:</h5>
<p>
The first argument is the value to write to the memory mapped I/O location.
The second argument is a pointer indicating the memory address to which the
data should be written.
</p>
<h5>Semantics:</h5>
<p>
The '<tt>llvm.writeio</tt>' intrinsic writes <i>value</i> to the memory mapped
I/O address specified by <i>pointer</i>. The value must be a
<a href="#t_firstclass">first class</a> type. However, certain architectures
may not support I/O on all first class types. For example, 32 bit processors
may only support I/O on data types that are 32 bits or less.
</p>
<p>
This intrinsic enforces an in-order memory model for llvm.readio and
llvm.writeio calls on machines that use dynamic scheduling. Dynamically
scheduled processors may execute loads and stores out of order, re-ordering at
run time accesses to memory mapped I/O registers. Using these intrinsics
ensures that accesses to memory mapped I/O registers occur in program order.
</p>
</div>
<!-- ======================================================================= --> <!-- ======================================================================= -->
<div class="doc_subsection"> <div class="doc_subsection">
<a name="int_libc">Standard C Library Intrinsics</a> <a name="int_libc">Standard C Library Intrinsics</a>