Lines Matching refs:handling

12 exception handling in LLVM.  It describes the format that LLVM exception
13 handling information takes, which is useful for those interested in creating
15 provides specific examples of what exception handling information is used for in
21 Exception handling for most programming languages is designed to recover from
23 exception handling should not interfere with the main flow of an application's
29 speculative exception handling code in the flow of an application's main
33 A more complete description of the Itanium ABI exception handling runtime
46 Setjmp/Longjmp (SJLJ) based exception handling uses LLVM intrinsics
48 exception handling.
60 In contrast to DWARF exception handling, which encodes exception regions and
61 frame information in out-of-line tables, SJLJ exception handling builds and
63 handling at the expense of slower execution when no exceptions are thrown. As
65 exception handling is generally preferred to SJLJ.
70 LLVM supports handling exceptions produced by the Windows runtime, but it
83 exception handling (e.g. C++), the exception frame contains a reference to an
85 not support exception handling (e.g. C), or if the exception needs to be
92 Because different programming languages have different behaviors when handling
93 exceptions, the exception handling ABI provides a mechanism for
94 supplying *personalities*. An exception handling personality is defined by
119 implementation of LLVM exception handling in terms of C++ examples.
124 Languages that support exception handling typically provide a ``throw``
293 handling scopes.
322 handling information at various points in generated code.
350 This intrinsic marks the beginning of catch handling code within the blocks
366 When used in the native Windows C++ exception handling implementation, this
383 This intrinsic marks the end of catch handling code within the current block,
399 When used in the native Windows C++ exception handling implementation, this
434 For SJLJ based exception handling, this intrinsic forces register saving for the
456 For SJLJ based exception handling, the ``llvm.eh.sjlj.longjmp`` intrinsic is
469 For SJLJ based exception handling, the ``llvm.eh.sjlj.lsda`` intrinsic returns
471 function. The SJLJ front-end code stores this address in the exception handling
481 For SJLJ based exception handling, the ``llvm.eh.sjlj.callsite`` intrinsic
489 There are two tables that are used by the exception handling runtime to
495 An exception handling frame ``eh_frame`` is very similar to the unwind frame
498 an exception handling frame for each function in a compile unit, plus a common
499 exception handling frame that defines information common to all functions in the
535 identifies frames with appropriate exception handling actions, and successively
542 handling the exception calls ``__cxa_end_catch`` to destroy the exception,
569 allocated in a child stack frame of the function handling the exception. If the
578 C++ exceptions and general purpose Windows exception handling. Because the C++
583 handling.
602 New exception handling instructions
615 The following new instructions are considered "exception handling pads", in that