From fb0a64a172fa405f7d0bcdd11226b99b433b8522 Mon Sep 17 00:00:00 2001 From: Duncan Sands Date: Mon, 16 Apr 2007 13:02:27 +0000 Subject: [PATCH] Fix typos. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@36124 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/ExceptionHandling.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ExceptionHandling.html b/docs/ExceptionHandling.html index 8303a49fab5..57b0c4d8488 100644 --- a/docs/ExceptionHandling.html +++ b/docs/ExceptionHandling.html @@ -121,8 +121,8 @@ exceptions, the exception handling ABI provides a mechanism for supplying personalities. An exception handling personality is defined by way of a personality function (ex. for C++ __gxx_personality_v0) which receives the context of the exception, an exception structure 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 common exception frame.

The organization of an exception table is language dependent. For C++, an @@ -195,7 +195,7 @@ unwinding of a throw.

The term used to define a the place where an invoke continues after an exception is called a landing pad. 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.