[llvm-commits] [llvm] r140631 - /llvm/trunk/docs/ExceptionHandling.html

Bill Wendling isanbard at gmail.com
Tue Sep 27 13:16:57 PDT 2011


Author: void
Date: Tue Sep 27 15:16:57 2011
New Revision: 140631

URL: http://llvm.org/viewvc/llvm-project?rev=140631&view=rev
Log:
Remove incorrect passage.

Modified:
    llvm/trunk/docs/ExceptionHandling.html

Modified: llvm/trunk/docs/ExceptionHandling.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/ExceptionHandling.html?rev=140631&r1=140630&r2=140631&view=diff
==============================================================================
--- llvm/trunk/docs/ExceptionHandling.html (original)
+++ llvm/trunk/docs/ExceptionHandling.html Tue Sep 27 15:16:57 2011
@@ -361,14 +361,10 @@
 <div>
 
 <p>The unwinder delegates the decision of whether to stop in a call frame to
-   that call frame's language-specific personality function. Not all personality
-   functions guarantee that they will stop to perform cleanups. For example, the
-   GNU C++ personality function doesn't do so unless the exception is actually
-   caught somewhere further up the stack. When using this personality to
-   implement EH for a language that guarantees that cleanups will always be run
-   (e.g. Ada), be sure to indicate a catch-all in the
-   <a href="LangRef.html#i_landingpad"><tt>landingpad</tt> instruction</a>
-   rather than just cleanups.</p>
+   that call frame's language-specific personality function. Not all unwinders
+   guarantee that they will stop to perform cleanups. For example, the GNU C++
+   unwinder doesn't do so unless the exception is actually caught somewhere
+   further up the stack.</p>
 
 <p>In order for inlining to behave correctly, landing pads must be prepared to
    handle selector results that they did not originally advertise. Suppose that





More information about the llvm-commits mailing list