From: Bill Wendling Date: Tue, 27 Sep 2011 10:37:28 +0000 (+0000) Subject: Remove some not-really-correct wording. X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=24771028a07f7cff91af537b15ac74b3452818d8;p=oota-llvm.git Remove some not-really-correct wording. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140600 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/ExceptionHandling.html b/docs/ExceptionHandling.html index 06cb2cf8197..95db367de43 100644 --- a/docs/ExceptionHandling.html +++ b/docs/ExceptionHandling.html @@ -261,7 +261,7 @@ and filter clauses. The exception is tested against the clauses sequentially from first to last. The selector value is a positive number if the exception matched a type info, a negative number if it matched a filter, - and zero if it matched to a cleanup. If nothing is matched, the behavior of + and zero if it matched a cleanup. If nothing is matched, the behavior of the program is undefined. If a type info matched, then the selector value is the index of the type info in the exception table, which can be obtained using the @@ -276,11 +276,6 @@ determine the index for a given type info. If the catch fails to match the selector then control is passed on to the next catch.

-

Note: Since the landing pad will not be used if there is no match in - the list of type info on the call to the landingpad instruction, - then neither the last catch nor catch all need to perform the check - against the selector.

-

Finally, the entry and exit of catch code is bracketed with calls to __cxa_begin_catch and __cxa_end_catch.