3 //! On Windows (currently only on MSVC), the default exception handling
4 //! mechanism is Structured Exception Handling (SEH). This is quite different
5 //! than Dwarf-based exception handling (e.g., what other unix platforms use) in
6 //! terms of compiler internals, so LLVM is required to have a good deal of
7 //! extra support for SEH.
9 //! In a nutshell, what happens here is:
11 //! 1. The `panic` function calls the standard Windows function
12 //! `_CxxThrowException` to throw a C++-like exception, triggering the
13 //! unwinding process.
14 //! 2. All landing pads generated by the compiler use the personality function
15 //! `__CxxFrameHandler3`, a function in the CRT, and the unwinding code in
16 //! Windows will use this personality function to execute all cleanup code on
18 //! 3. All compiler-generated calls to `invoke` have a landing pad set as a
19 //! `cleanuppad` LLVM instruction, which indicates the start of the cleanup
20 //! routine. The personality (in step 2, defined in the CRT) is responsible
21 //! for running the cleanup routines.
22 //! 4. Eventually the "catch" code in the `try` intrinsic (generated by the
23 //! compiler) is executed and indicates that control should come back to
24 //! Rust. This is done via a `catchswitch` plus a `catchpad` instruction in
25 //! LLVM IR terms, finally returning normal control to the program with a
26 //! `catchret` instruction.
28 //! Some specific differences from the gcc-based exception handling are:
30 //! * Rust has no custom personality function, it is instead *always*
31 //! `__CxxFrameHandler3`. Additionally, no extra filtering is performed, so we
32 //! end up catching any C++ exceptions that happen to look like the kind we're
33 //! throwing. Note that throwing an exception into Rust is undefined behavior
34 //! anyway, so this should be fine.
35 //! * We've got some data to transmit across the unwinding boundary,
36 //! specifically a `Box<dyn Any + Send>`. Like with Dwarf exceptions
37 //! these two pointers are stored as a payload in the exception itself. On
38 //! MSVC, however, there's no need for an extra heap allocation because the
39 //! call stack is preserved while filter functions are being executed. This
40 //! means that the pointers are passed directly to `_CxxThrowException` which
41 //! are then recovered in the filter function to be written to the stack frame
42 //! of the `try` intrinsic.
44 //! [win64]: http://msdn.microsoft.com/en-us/library/1eyas8tf.aspx
45 //! [llvm]: http://llvm.org/docs/ExceptionHandling.html#background-on-windows-exceptions
47 #![allow(nonstandard_style)]
48 #![allow(private_no_mangle_fns)]
50 use alloc::boxed::Box;
54 use libc::{c_int, c_uint, c_void};
56 // First up, a whole bunch of type definitions. There's a few platform-specific
57 // oddities here, and a lot that's just blatantly copied from LLVM. The purpose
58 // of all this is to implement the `panic` function below through a call to
59 // `_CxxThrowException`.
61 // This function takes two arguments. The first is a pointer to the data we're
62 // passing in, which in this case is our trait object. Pretty easy to find! The
63 // next, however, is more complicated. This is a pointer to a `_ThrowInfo`
64 // structure, and it generally is just intended to just describe the exception
67 // Currently the definition of this type [1] is a little hairy, and the main
68 // oddity (and difference from the online article) is that on 32-bit the
69 // pointers are pointers but on 64-bit the pointers are expressed as 32-bit
70 // offsets from the `__ImageBase` symbol. The `ptr_t` and `ptr!` macro in the
71 // modules below are used to express this.
73 // The maze of type definitions also closely follows what LLVM emits for this
74 // sort of operation. For example, if you compile this C++ code on MSVC and emit
77 // #include <stdint.h>
79 // struct rust_panic {
84 // rust_panic a = {0, 1};
88 // That's essentially what we're trying to emulate. Most of the constant values
89 // below were just copied from LLVM,
91 // In any case, these structures are all constructed in a similar manner, and
92 // it's just somewhat verbose for us.
94 // [1]: http://www.geoffchappell.com/studies/msvc/language/predefined/
96 #[cfg(target_arch = "x86")]
99 pub type ptr_t = *mut u8;
102 (0) => (core::ptr::null_mut());
103 ($e:expr) => ($e as *mut u8);
107 #[cfg(any(target_arch = "x86_64", target_arch = "arm"))]
110 pub type ptr_t = u32;
113 pub static __ImageBase: u8;
119 (($e as usize) - (&imp::__ImageBase as *const _ as usize)) as u32
125 pub struct _ThrowInfo {
126 pub attributes: c_uint,
127 pub pnfnUnwind: imp::ptr_t,
128 pub pForwardCompat: imp::ptr_t,
129 pub pCatchableTypeArray: imp::ptr_t,
133 pub struct _CatchableTypeArray {
134 pub nCatchableTypes: c_int,
135 pub arrayOfCatchableTypes: [imp::ptr_t; 1],
139 pub struct _CatchableType {
140 pub properties: c_uint,
141 pub pType: imp::ptr_t,
142 pub thisDisplacement: _PMD,
143 pub sizeOrOffset: c_int,
144 pub copy_function: imp::ptr_t,
155 pub struct _TypeDescriptor {
156 pub pVFTable: *const u8,
161 // Note that we intentionally ignore name mangling rules here: we don't want C++
162 // to be able to catch Rust panics by simply declaring a `struct rust_panic`.
163 const TYPE_NAME: [u8; 11] = *b"rust_panic\0";
165 static mut THROW_INFO: _ThrowInfo = _ThrowInfo {
168 pForwardCompat: ptr!(0),
169 pCatchableTypeArray: ptr!(0),
172 static mut CATCHABLE_TYPE_ARRAY: _CatchableTypeArray = _CatchableTypeArray {
174 arrayOfCatchableTypes: [ptr!(0)],
177 static mut CATCHABLE_TYPE: _CatchableType = _CatchableType {
180 thisDisplacement: _PMD {
185 sizeOrOffset: mem::size_of::<[u64; 2]>() as c_int,
186 copy_function: ptr!(0),
190 // The leading `\x01` byte here is actually a magical signal to LLVM to
191 // *not* apply any other mangling like prefixing with a `_` character.
193 // This symbol is the vtable used by C++'s `std::type_info`. Objects of type
194 // `std::type_info`, type descriptors, have a pointer to this table. Type
195 // descriptors are referenced by the C++ EH structures defined above and
196 // that we construct below.
197 #[link_name = "\x01??_7type_info@@6B@"]
198 static TYPE_INFO_VTABLE: *const u8;
201 // We use #[lang = "eh_catch_typeinfo"] here as this is the type descriptor which
202 // we'll use in LLVM's `catchpad` instruction which ends up also being passed as
203 // an argument to the C++ personality function.
205 // Again, I'm not entirely sure what this is describing, it just seems to work.
206 #[cfg_attr(not(test), lang = "eh_catch_typeinfo")]
207 static mut TYPE_DESCRIPTOR: _TypeDescriptor = _TypeDescriptor {
208 pVFTable: unsafe { &TYPE_INFO_VTABLE } as *const _ as *const _,
209 spare: core::ptr::null_mut(),
213 pub unsafe fn panic(data: Box<dyn Any + Send>) -> u32 {
214 use core::intrinsics::atomic_store;
216 // _CxxThrowException executes entirely on this stack frame, so there's no
217 // need to otherwise transfer `data` to the heap. We just pass a stack
218 // pointer to this function.
220 // The first argument is the payload being thrown (our two pointers), and
221 // the second argument is the type information object describing the
222 // exception (constructed above).
223 let ptrs = mem::transmute::<_, raw::TraitObject>(data);
224 let mut ptrs = [ptrs.data as u64, ptrs.vtable as u64];
225 let ptrs_ptr = ptrs.as_mut_ptr();
226 let throw_ptr = ptrs_ptr as *mut _;
228 // This... may seems surprising, and justifiably so. On 32-bit MSVC the
229 // pointers between these structure are just that, pointers. On 64-bit MSVC,
230 // however, the pointers between structures are rather expressed as 32-bit
231 // offsets from `__ImageBase`.
233 // Consequently, on 32-bit MSVC we can declare all these pointers in the
234 // `static`s above. On 64-bit MSVC, we would have to express subtraction of
235 // pointers in statics, which Rust does not currently allow, so we can't
238 // The next best thing, then is to fill in these structures at runtime
239 // (panicking is already the "slow path" anyway). So here we reinterpret all
240 // of these pointer fields as 32-bit integers and then store the
241 // relevant value into it (atomically, as concurrent panics may be
242 // happening). Technically the runtime will probably do a nonatomic read of
243 // these fields, but in theory they never read the *wrong* value so it
244 // shouldn't be too bad...
246 // In any case, we basically need to do something like this until we can
247 // express more operations in statics (and we may never be able to).
248 atomic_store(&mut THROW_INFO.pCatchableTypeArray as *mut _ as *mut u32,
249 ptr!(&CATCHABLE_TYPE_ARRAY as *const _) as u32);
250 atomic_store(&mut CATCHABLE_TYPE_ARRAY.arrayOfCatchableTypes[0] as *mut _ as *mut u32,
251 ptr!(&CATCHABLE_TYPE as *const _) as u32);
252 atomic_store(&mut CATCHABLE_TYPE.pType as *mut _ as *mut u32,
253 ptr!(&TYPE_DESCRIPTOR as *const _) as u32);
257 pub fn _CxxThrowException(pExceptionObject: *mut c_void, pThrowInfo: *mut u8) -> !;
260 _CxxThrowException(throw_ptr,
261 &mut THROW_INFO as *mut _ as *mut _);
264 pub fn payload() -> [u64; 2] {
268 pub unsafe fn cleanup(payload: [u64; 2]) -> Box<dyn Any + Send> {
269 mem::transmute(raw::TraitObject {
270 data: payload[0] as *mut _,
271 vtable: payload[1] as *mut _,
275 // This is required by the compiler to exist (e.g., it's a lang item), but
276 // it's never actually called by the compiler because __C_specific_handler
277 // or _except_handler3 is the personality function that is always used.
278 // Hence this is just an aborting stub.
279 #[lang = "eh_personality"]
281 fn rust_eh_personality() {
282 unsafe { core::intrinsics::abort() }