Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / d40bc4ad433b45445bbdf2d187f853d67cb9eb9a / . / docs / ExceptionHandling.html
blob: 0b1c651704149634e01a00fc678c6ccb6fd39154 [file] [log] [blame]
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4<head>
5 <title>Exception Handling in LLVM</title>
6 <link rel="stylesheet" href="llvm.css" type="text/css">
7</head>
8<body>
9
10<div class="doc_title">Exception Handling in LLVM</div>
11
12<table class="layout" style="width:100%">
13 <tr class="layout">
14 <td class="left">
15<ul>
16 <li><a href="#introduction">Introduction</a>
17 <ol>
18 <li><a href="#itanium">Itanium ABI Zero-cost Exception Handling</a></li>
19 <li><a href="#overview">Overview</a></li>
20 </ol></li>
21 <li><a href="#codegen">LLVM Code Generation</a>
22 <ol>
23 <li><a href="#throw">Throw</a></li>
24 <li><a href="#try_catch">Try/Catch</a></li>
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]25 <li><a href="#cleanups">Cleanups</a></li>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]26 <li><a href="#throw_filters">Throw Filters</a></li>
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]27 <li><a href="#restrictions">Restrictions</a></li>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]28 </ol></li>
Duncan Sands8036ca42007-03-30 12:22:09 +0000[diff] [blame]29 <li><a href="#format_common_intrinsics">Exception Handling Intrinsics</a>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]30 <ol>
31 <li><a href="#llvm_eh_exception"><tt>llvm.eh.exception</tt></a></li>
32 <li><a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a></li>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]33 <li><a href="#llvm_eh_typeid_for"><tt>llvm.eh.typeid.for</tt></a></li>
34 </ol></li>
35 <li><a href="#asm">Asm Table Formats</a>
36 <ol>
37 <li><a href="#unwind_tables">Exception Handling Frame</a></li>
38 <li><a href="#exception_tables">Exception Tables</a></li>
39 </ol></li>
40 <li><a href="#todo">ToDo</a></li>
41</ul>
42</td>
43</tr></table>
44
45<div class="doc_author">
46 <p>Written by <a href="mailto:jlaskey@mac.com">Jim Laskey</a></p>
47</div>
48
49
50<!-- *********************************************************************** -->
51<div class="doc_section"><a name="introduction">Introduction</a></div>
52<!-- *********************************************************************** -->
53
54<div class="doc_text">
55
56<p>This document is the central repository for all information pertaining to
57exception handling in LLVM. It describes the format that LLVM exception
58handling information takes, which is useful for those interested in creating
59front-ends or dealing directly with the information. Further, this document
60provides specific examples of what exception handling information is used for
61C/C++.</p>
62
63</div>
64
65<!-- ======================================================================= -->
66<div class="doc_subsection">
67 <a name="itanium">Itanium ABI Zero-cost Exception Handling</a>
68</div>
69
70<div class="doc_text">
71
72<p>Exception handling for most programming languages is designed to recover from
73conditions that rarely occur during general use of an application. To that end,
74exception handling should not interfere with the main flow of an
Bill Wendlingd40bc4a2007-09-22 10:17:08 +0000[diff] [blame^]75application's algorithm by performing checkpointing tasks such as saving
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]76the current pc or register state.</p>
77
78<p>The Itanium ABI Exception Handling Specification defines a methodology for
79providing outlying data in the form of exception tables without inlining
Bill Wendlingd40bc4a2007-09-22 10:17:08 +0000[diff] [blame^]80speculative exception handling code in the flow of an application's main
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]81algorithm. Thus, the specification is said to add "zero-cost" to the normal
82execution of an application.</p>
83
84<p>A more complete description of the Itanium ABI exception handling runtime
85support of can be found at <a
86href="http://www.codesourcery.com/cxx-abi/abi-eh.html">Itanium C++ ABI:
Bill Wendlingd40bc4a2007-09-22 10:17:08 +0000[diff] [blame^]87Exception Handling.</a> A description of the exception frame format can be found
88at <a href="http://refspecs.freestandards.org/LSB_3.0.0/LSB-Core-generic/LSB-
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]89Core-generic/ehframechpt.html">Exception Frames</a>, with details of the Dwarf
90specification at <a href="http://www.eagercon.com/dwarf/dwarf3std.htm">Dwarf 3
91Standard.</a> A description for the C++ exception table formats can be found at
92<a href="http://www.codesourcery.com/cxx-abi/exceptions.pdf">Exception Handling
93Tables.</a></p>
94
95</div>
96
97<!-- ======================================================================= -->
98<div class="doc_subsection">
99 <a name="overview">Overview</a>
100</div>
101
102<div class="doc_text">
103
104<p>When an exception is thrown in llvm code, the runtime does a best effort to
105find a handler suited to process the circumstance.</p>
106
107<p>The runtime first attempts to find an <i>exception frame</i> corresponding to
108the function where the exception was thrown. If the programming language (ex.
109C++) supports exception handling, the exception frame contains a reference to an
110exception table describing how to process the exception. If the language (ex.
111C) does not support exception handling or if the exception needs to be forwarded
112to a prior activation, the exception frame contains information about how to
113unwind the current activation and restore the state of the prior activation.
114This process is repeated until the exception is handled. If the exception is
115not handled and no activations remain, then the application is terminated with
116an appropriate error message.</p>
117
118<p>Since different programming languages have different behaviors when handling
119exceptions, the exception handling ABI provides a mechanism for supplying
120<i>personalities.</i> An exception handling personality is defined by way of a
121<i>personality function</i> (ex. for C++ <tt>__gxx_personality_v0</tt>) which
122receives the context of the exception, an <i>exception structure</i> containing
Duncan Sandsfb0a64a2007-04-16 13:02:27 +0000[diff] [blame]123the exception object type and value, and a reference to the exception table for
124the current function. The personality function for the current compile unit is
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]125specified in a <i>common exception frame</i>.</p>
126
127<p>The organization of an exception table is language dependent. For C++, an
128exception table is organized as a series of code ranges defining what to do if
129an exception occurs in that range. Typically, the information associated with a
130range defines which types of exception objects (using C++ <i>type info</i>) that
131are handled in that range, and an associated action that should take place.
132Actions typically pass control to a <i>landing pad</i>.</p>
133
134<p>A landing pad corresponds to the code found in the catch portion of a
135try/catch sequence. When execution resumes at a landing pad, it receives the
136exception structure and a selector corresponding to the <i>type</i> of exception
137thrown. The selector is then used to determine which catch should actually
138process the exception.</p>
139
140</div>
141
142<!-- ======================================================================= -->
143<div class="doc_section">
144 <a name="codegen">LLVM Code Generation</a>
145</div>
146
147<div class="doc_text">
148
149<p>At the time of this writing, only C++ exception handling support is available
150in LLVM. So the remainder of this document will be somewhat C++-centric.</p>
151
152<p>From the C++ developers perspective, exceptions are defined in terms of the
153<tt>throw</tt> and <tt>try/catch</tt> statements. In this section we will
154describe the implementation of llvm exception handling in terms of C++
155examples.</p>
156
157</div>
158
159<!-- ======================================================================= -->
160<div class="doc_subsection">
161 <a name="throw">Throw</a>
162</div>
163
164<div class="doc_text">
165
166<p>Languages that support exception handling typically provide a <tt>throw</tt>
167operation to initiate the exception process. Internally, a throw operation
168breaks down into two steps. First, a request is made to allocate exception
169space for an exception structure. This structure needs to survive beyond the
170current activation. This structure will contain the type and value of the
171object being thrown. Second, a call is made to the runtime to raise the
172exception, passing the exception structure as an argument.</p>
173
174<p>In C++, the allocation of the exception structure is done by the
175<tt>__cxa_allocate_exception</tt> runtime function. The exception raising is
176handled by <tt>__cxa_throw</tt>. The type of the exception is represented using
177a C++ RTTI type info structure.</p>
178
179</div>
180
181<!-- ======================================================================= -->
182<div class="doc_subsection">
183 <a name="try_catch">Try/Catch</a>
184</div>
185
186<div class="doc_text">
187
Duncan Sandsb0a1cbf2007-04-14 12:30:27 +0000[diff] [blame]188<p>A call within the scope of a try statement can potentially raise an exception.
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]189In those circumstances, the LLVM C++ front-end replaces the call with an
190<tt>invoke</tt> instruction. Unlike a call, the invoke has two potential
191continuation points; where to continue when the call succeeds as per normal, and
192where to continue if the call raises an exception, either by a throw or the
193unwinding of a throw.</p>
194
195<p>The term used to define a the place where an invoke continues after an
196exception is called a <i>landing pad</i>. LLVM landing pads are conceptually
Duncan Sandsfb0a64a2007-04-16 13:02:27 +0000[diff] [blame]197alternative function entry points where a exception structure reference and a type
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]198info index are passed in as arguments. The landing pad saves the exception
199structure reference and then proceeds to select the catch block that corresponds
200to the type info of the exception object.</p>
201
202<p>Two llvm intrinsic functions are used convey information about the landing
203pad to the back end.</p>
204
205<p><a href="#llvm_eh_exception"><tt>llvm.eh.exception</tt></a> takes no
206arguments and returns the exception structure reference. The backend replaces
207this intrinsic with the code that accesses the first argument of a call. The
208LLVM C++ front end generates code to save this value in an alloca location for
209further use in the landing pad and catch code.</p>
210
211<p><a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> takes a minimum of
212three arguments. The first argument is the reference to the exception
213structure. The second argument is a reference to the personality function to be
Duncan Sandscf26d7c2007-07-04 20:52:51 +0000[diff] [blame]214used for this try catch sequence. Each of the remaining arguments is either a
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]215reference to the type info for a catch statement,
216a <a href="#throw_filters">filter</a> expression,
217or the number zero representing a <a href="#cleanups">cleanup</a>.
Duncan Sandscf26d7c2007-07-04 20:52:51 +0000[diff] [blame]218The exception is tested against the arguments sequentially from first to last.
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]219The result of the <a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> is a
220positive number if the exception matched a type info, a negative number if it matched
221a filter, and zero if it matched a cleanup. If nothing is matched, the behaviour of
222the program is <a href="#restrictions">undefined</a>.
223The LLVM C++ front end generates code to save the selector value in an alloca
224location for further use in the landing pad and catch code.
225If a type info matched then the selector value is the index of the type info in
226the exception table, which can be obtained using the
227<a href="#llvm_eh_typeid_for"><tt>llvm.eh.typeid.for</tt></a> intrinsic.</p>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]228
229<p>Once the landing pad has the type info selector, the code branches to the
230code for the first catch. The catch then checks the value of the type info
231selector against the index of type info for that catch. Since the type info
232index is not known until all the type info have been gathered in the backend,
233the catch code will call the <a
234href="#llvm_eh_typeid_for"><tt>llvm.eh.typeid.for</tt></a> intrinsic to
235determine the index for a given type info. If the catch fails to match the
236selector then control is passed on to the next catch. Note: Since the landing
237pad will not be used if there is no match in the list of type info on the call
238to <a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a>, then neither the
239last catch nor <i>catch all</i> need to perform the the check against the
240selector.</p>
241
242<p>Finally, the entry and exit of catch code is bracketed with calls to
243<tt>__cxa_begin_catch</tt> and <tt>__cxa_end_catch</tt>.
244<tt>__cxa_begin_catch</tt> takes a exception structure reference as an argument
Bill Wendlingd40bc4a2007-09-22 10:17:08 +0000[diff] [blame^]245and returns the value of the exception object. <tt>__cxa_end_catch</tt>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]246takes a exception structure reference as an argument. This function clears the
247exception from the exception space. Note: a rethrow from within the catch may
248replace this call with a <tt>__cxa_rethrow</tt>.</p>
249
250</div>
251
252<!-- ======================================================================= -->
253<div class="doc_subsection">
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]254 <a name="cleanups">Cleanups</a>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]255</div>
256
257<div class="doc_text">
258
259<p>To handle destructors and cleanups in try code, control may not run directly
260from a landing pad to the first catch. Control may actually flow from the
261landing pad to clean up code and then to the first catch. Since the required
262clean up for each invoke in a try may be different (ex., intervening
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]263constructor), there may be several landing pads for a given try. If cleanups
264need to be run, the number zero should be passed as the last
265<a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> argument.
266However for C++ a <tt>null i8*</tt> <a href="#restrictions">must</a> be passed
267instead.
268</p>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]269
270</div>
271
272<!-- ======================================================================= -->
273<div class="doc_subsection">
274 <a name="throw_filters">Throw Filters</a>
275</div>
276
277<div class="doc_text">
278
279<p>C++ allows the specification of which exception types that can be thrown from
280a function. To represent this a top level landing pad may exist to filter out
281invalid types. To express this in LLVM code the landing pad will call <a
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]282href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a>. The arguments are the
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]283length of the filter expression (the number of type infos plus one), followed by
284the type infos themselves.
Duncan Sandscf26d7c2007-07-04 20:52:51 +0000[diff] [blame]285<a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> will return a negative
286value if the exception does not match any of the type infos. If no match is
287found then a call to <tt>__cxa_call_unexpected</tt> should be made, otherwise
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]288<tt>_Unwind_Resume</tt>. Each of these functions require a reference to the
289exception structure.</p>
290
291</div>
292
293<!-- ======================================================================= -->
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]294<div class="doc_subsection">
295 <a name="restrictions">Restrictions</a>
296</div>
297
298<div class="doc_text">
299
300<p>The semantics of the invoke instruction require that any exception that
301unwinds through an invoke call should result in a branch to the invoke's unwind
302label. However such a branch will only happen if the
303<a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> matches.
304Thus in order to ensure correct operation, the front-end must only generate
305<a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> calls that are
306guaranteed to always match whatever exception unwinds through the invoke.
307For most languages it is enough to pass zero, indicating the presence of
308a <a href="#cleanups">cleanup</a>, as the last
309<a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> argument.
310However for C++ this is not sufficient, because the C++ personality function
311will terminate the program if it detects that unwinding the exception only
312results in matches with cleanups. For C++ a <tt>null i8*</tt> should
313be passed as the last
314<a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> argument instead.
315This is interpreted as a catch-all by the C++ personality function, and will
316always match.
317</p>
318
319</div>
320
321<!-- ======================================================================= -->
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]322<div class="doc_section">
Duncan Sands8036ca42007-03-30 12:22:09 +0000[diff] [blame]323 <a name="format_common_intrinsics">Exception Handling Intrinsics</a>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]324</div>
325
326<div class="doc_text">
327
328<p>LLVM uses several intrinsic functions (name prefixed with "llvm.eh") to
329provide exception handling information at various points in generated code.</p>
330
331</div>
332
333<!-- ======================================================================= -->
334<div class="doc_subsubsection">
335 <a name="llvm_eh_exception">llvm.eh.exception</a>
336</div>
337
338<div class="doc_text">
339<pre>
340 i8* %<a href="#llvm_eh_exception">llvm.eh.exception</a>( )
341</pre>
342
343<p>This intrinsic indicates that the exception structure is available at this
344point in the code. The backend will replace this intrinsic with code to fetch
345the first argument of a call. The effect is that the intrinsic result is the
346exception structure reference.</p>
347
348</div>
349
350<!-- ======================================================================= -->
351<div class="doc_subsubsection">
352 <a name="llvm_eh_selector">llvm.eh.selector</a>
353</div>
354
355<div class="doc_text">
356<pre>
Anton Korobeynikov8806c7b2007-09-07 11:39:35 +0000[diff] [blame]357 i32 %<a href="#llvm_eh_selector">llvm.eh.selector.i32</a>(i8*, i8*, i8*, ...)
358 i64 %<a href="#llvm_eh_selector">llvm.eh.selector.i64</a>(i8*, i8*, i8*, ...)
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]359</pre>
360
361<p>This intrinsic indicates that the exception selector is available at this
362point in the code. The backend will replace this intrinsic with code to fetch
363the second argument of a call. The effect is that the intrinsic result is the
364exception selector.</p>
365
366<p><a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> takes a minimum of
367three arguments. The first argument is the reference to the exception
368structure. The second argument is a reference to the personality function to be
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]369used for this try catch sequence. Each of the remaining arguments is either a
370reference to the type info for a catch statement,
371a <a href="#throw_filters">filter</a> expression,
372or the number zero representing a <a href="#cleanups">cleanup</a>.
Duncan Sandscf26d7c2007-07-04 20:52:51 +0000[diff] [blame]373The exception is tested against the arguments sequentially from first to last.
Duncan Sands6590b042007-08-27 15:47:50 +0000[diff] [blame]374The result of the <a href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a> is a
375positive number if the exception matched a type info, a negative number if it matched
376a filter, and zero if it matched a cleanup. If nothing is matched, the behaviour of
377the program is <a href="#restrictions">undefined</a>.
378If a type info matched then the selector value is the index of the type info in
379the exception table, which can be obtained using the
380<a href="#llvm_eh_typeid_for"><tt>llvm.eh.typeid.for</tt></a> intrinsic.</p>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]381
382</div>
383
384<!-- ======================================================================= -->
385<div class="doc_subsubsection">
386 <a name="llvm_eh_typeid_for">llvm.eh.typeid.for</a>
387</div>
388
389<div class="doc_text">
390<pre>
Anton Korobeynikov8806c7b2007-09-07 11:39:35 +0000[diff] [blame]391 i32 %<a href="#llvm_eh_typeid_for">llvm.eh.typeid.for.i32</a>(i8*)
392 i64 %<a href="#llvm_eh_typeid_for">llvm.eh.typeid.for.i64</a>(i8*)
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]393</pre>
394
395<p>This intrinsic returns the type info index in the exception table of the
396current function. This value can be used to compare against the result of <a
397href="#llvm_eh_selector"><tt>llvm.eh.selector</tt></a>. The single argument is
398a reference to a type info.</p>
399
400</div>
401
402<!-- ======================================================================= -->
403<div class="doc_section">
404 <a name="asm">Asm Table Formats</a>
405</div>
406
407<div class="doc_text">
408
409<p>There are two tables that are used by the exception handling runtime to
410determine which actions should take place when an exception is thrown.</p>
411
412</div>
413
414<!-- ======================================================================= -->
415<div class="doc_subsection">
416 <a name="unwind_tables">Exception Handling Frame</a>
417</div>
418
419<div class="doc_text">
420
421<p>An exception handling frame <tt>eh_frame</tt> is very similar to the unwind
422frame used by dwarf debug info. The frame contains all the information
423necessary to tear down the current frame and restore the state of the prior
424frame. There is an exception handling frame for each function in a compile
425unit, plus a common exception handling frame that defines information common to
426all functions in the unit.</p>
427
428<p>Todo - Table details here.</p>
429
430</div>
431
432<!-- ======================================================================= -->
433<div class="doc_subsection">
434 <a name="exception_tables">Exception Tables</a>
435</div>
436
437<div class="doc_text">
438
439<p>An exception table contains information about what actions to take when an
Bill Wendlingd40bc4a2007-09-22 10:17:08 +0000[diff] [blame^]440exception is thrown in a particular part of a function's code. There is
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]441one exception table per function except leaf routines and functions that have
442only calls to non-throwing functions will not need an exception table.</p>
443
444<p>Todo - Table details here.</p>
445
446</div>
447
448<!-- ======================================================================= -->
449<div class="doc_section">
450 <a name="todo">ToDo</a>
451</div>
452
453<div class="doc_text">
454
455<ol>
456
Bill Wendlingd40bc4a2007-09-22 10:17:08 +0000[diff] [blame^]457<li><p>Testing/Testing/Testing.</p></li>
Jim Laskeyd0d39b62007-03-14 19:29:42 +0000[diff] [blame]458
459</ol>
460
461</div>
462
463<!-- *********************************************************************** -->
464
465<hr>
466<address>
467 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
468 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
469 <a href="http://validator.w3.org/check/referer"><img
470 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
471
472 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
473 <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
474 Last modified: $Date$
475</address>
476
477</body>
478</html>