Displaying 3 results from an estimated 3 matches for "dtor3".
Did you mean:
dtor
2012 Apr 08
0
[LLVMdev] Catching C++ exceptions, cleaning up, rethrowing
...= landingpad %0 personality i32 (...)* @__gxx_personality_v0
> cleanup
> store %0 %5, %0* %caught_result_storage, align 8
> store i8 1, i8* %exception_caught_flag, align 1
> br label %exit
>
> dtor: ; preds = %unwind2, %dtor3
> %6 = phi %0 [ %9, %unwind2 ], [ %10, %dtor3 ]
> %7 = phi i8 [ 1, %unwind2 ], [ %11, %dtor3 ]
> call void @thunk_item_M_delete(void* %0)
> br label %exit
>
> normal1: ; preds = %normal
> %8 = bitcast %singleton_iterator* %x_i...
2012 Apr 08
2
[LLVMdev] Catching C++ exceptions, cleaning up, rethrowing
On Apr 4, 2012, at 9:32 PM, Paul J. Lucas wrote:
> On Mar 23, 2012, at 4:46 PM, Bill Wendling wrote:
[...]
> This all seems to work just fine. I can throw a C++ exception either in a C++ object's constructor or in an ordinary member function and the stack unwinds correctly (the object's destructors are called) and the exception is propagated back up the C++ code that called the
2012 Apr 09
5
[LLVMdev] Catching C++ exceptions, cleaning up, rethrowing
...produces is more verbose, but after optimizations, code-gen typically doesn't produce a lot of code for these sequences.
>> store i8 1, i8* %exception_caught_flag, align 1
>> br label %exit
>>
>> dtor: ; preds = %unwind2, %dtor3
>> %6 = phi %0 [ %9, %unwind2 ], [ %10, %dtor3 ]
>> %7 = phi i8 [ 1, %unwind2 ], [ %11, %dtor3 ]
>> call void @thunk_item_M_delete(void* %0)
>> br label %exit
>>
>> normal1: ; preds = %normal
>> %8 = bitcast %s...