From: John Criswell <criswell@uiuc.edu>
Date: Fri, 25 Jun 2004 16:42:50 +0000 (+0000)
Subject: Removed the interrupt_handler instrinsic section that I accidently added
X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=f5076133a94a08e385e5dd1b0c75f2d32fe542ab;p=oota-llvm.git

Removed the interrupt_handler instrinsic section that I accidently added
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
---

diff --git a/docs/LangRef.html b/docs/LangRef.html
index acc6a3bbd50..1b9dc458ccf 100644
--- a/docs/LangRef.html
+++ b/docs/LangRef.html
@@ -2357,53 +2357,6 @@ ensures that accesses to memory mapped I/O registers occur in program order.
 
 </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">
   <a name="int_libc">Standard C Library Intrinsics</a>