don't use binutils 2.17

[oota-llvm.git] / docs / ExceptionHandling.html

diff --git a/docs/ExceptionHandling.html b/docs/ExceptionHandling.html
index d515b4cd0ed4d0c51113eeb0efa59a956c296362..57b0c4d84887555b480bed8cabfa2007842aafcb 100644 (file)
--- a/docs/ExceptionHandling.html
+++ b/docs/ExceptionHandling.html
@@ -22,10 +22,10 @@
   <ol>
     <li><a href="#throw">Throw</a></li>
     <li><a href="#try_catch">Try/Catch</a></li>
-    <li><a href="#finally">Finallys</a></li>
+    <li><a href="#finallys">Finallys</a></li>
     <li><a href="#throw_filters">Throw Filters</a></li>
   </ol></li>
-  <li><a href="#intrinsics">Exception Handling Intrinsics</a>
+  <li><a href="#format_common_intrinsics">Exception Handling Intrinsics</a>
   <ol>
        <li><a href="#llvm_eh_exception"><tt>llvm.eh.exception</tt></a></li>
        <li><a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a></li>
@@ -121,8 +121,8 @@ exceptions, the exception handling ABI provides a mechanism for supplying
 <i>personalities.</i> An exception handling personality is defined by way of a
 <i>personality function</i> (ex. for C++ <tt>__gxx_personality_v0</tt>) which
 receives the context of the exception, an <i>exception structure</i> containing
-the exception object type and value, and a reference the exception table for the
-current function.  The personality function for the current compile unit is
+the exception object type and value, and a reference to the exception table for
+the current function.  The personality function for the current compile unit is
 specified in a <i>common exception frame</i>.</p>
 
 <p>The organization of an exception table is language dependent.  For C++, an
@@ -186,7 +186,7 @@ a C++ RTTI type info structure.</p>
 
 <div class="doc_text">
 
-<p>A call within the scope of a try statement can potential raise an exception.
+<p>A call within the scope of a try statement can potentially raise an exception.
 In those circumstances, the LLVM C++ front-end replaces the call with an
 <tt>invoke</tt> instruction.  Unlike a call, the invoke has two potential
 continuation points; where to continue when the call succeeds as per normal, and
@@ -195,7 +195,7 @@ unwinding of a throw.</p>
 
 <p>The term used to define a the place where an invoke continues after an
 exception is called a <i>landing pad</i>.  LLVM landing pads are conceptually
-alternative entry points into where a exception structure reference and a type
+alternative function entry points where a exception structure reference and a type
 info index are passed in as arguments.  The landing pad saves the exception
 structure reference and then proceeds to select the catch block that corresponds
 to the type info of the exception object.</p>
@@ -281,7 +281,7 @@ exception structure.</p>
 
 <!-- ======================================================================= -->
 <div class="doc_section">
-  <a name="intrinsics">Exception Handling Intrinsics</a>
+  <a name="format_common_intrinsics">Exception Handling Intrinsics</a>
 </div>
 
 <div class="doc_text">