Displaying 5 results from an estimated 5 matches for "handlerdata".
Did you mean:
handler_data
2014 May 12
3
[LLVMdev] Libc++abi tests on ARM
On 12 May 2014 20:20, Logan Chien <tzuhsiang.chien at gmail.com> wrote:
> There is a known issue in the code generated by LLVM.
> As a workaround, I am adding "-funwind-tables" to compile the unit tests.
I thought I had fixed all of them. Do you have a bug number?
> BTW, the LLVM revision which I am using is r207501.
> It seems that the recent master has come
2014 Nov 14
2
[LLVMdev] RFC: How to represent SEH (__try / __except) in LLVM IR
...out the terminate and resume calls for the time being, I see my personality function being called twice -- first for the C++ exception (Exception code == 0xe06d7363) and once for the unwind. So now I just need to figure out how to get a pointer to a cleanup function into the DispatcherContext->HandlerData, which must be where the extra stuff in the landingpad comes in, right?
Anyway, I think I’m making progress. :-)
-Andy
From: Reid Kleckner [mailto:rnk at google.com]
Sent: Thursday, November 13, 2014 4:22 PM
To: Kaylor, Andrew
Cc: LLVM Developers Mailing List; John McCall
Subject: Re: [LLVMdev]...
2013 Feb 04
2
[LLVMdev] ARM c++ exceptions handling not working with clang/llvm-3.2?
...printf
.LEHE2:
bl __cxa_end_catch
mov r3, #0
mov r0, r3
sub sp, fp, #4
ldmfd sp!, {fp, lr}
bx lr
.L10:
.align 2
.L9:
.word _ZTIi
.word .LC0
.global __gxx_personality_v0
.personality __gxx_personality_v0
.handlerdata
.align 2
.LLSDA6:
.byte 0xff
.byte 0
.uleb128 .LLSDATT6-.LLSDATTD6
.LLSDATTD6:
.byte 0x1
.uleb128 .LLSDACSE6-.LLSDACSB6
.LLSDACSB6:
.uleb128 .LEHB0-.LFB6
.uleb128 .LEHE0-.LEHB0
.uleb128 .L7-.LFB6
.uleb128 0x1
.uleb128 .LEHB1-.LFB6...
2014 Nov 18
2
[LLVMdev] RFC: How to represent SEH (__try / __except) in LLVM IR
...out the terminate and resume calls for the time being, I see my personality function being called twice -- first for the C++ exception (Exception code == 0xe06d7363) and once for the unwind. So now I just need to figure out how to get a pointer to a cleanup function into the DispatcherContext->HandlerData, which must be where the extra stuff in the landingpad comes in, right?
>
>
> It's got some docs here:
> http://llvm.org/docs/ExceptionHandling.html#overview <http://llvm.org/docs/ExceptionHandling.html#overview>
>
> The two values are the exception pointer and the se...
2014 Nov 13
2
[LLVMdev] RFC: How to represent SEH (__try / __except) in LLVM IR
Thanks for the additional information.
Right now I’m experimenting with a mix of code compiled with MSVC and code compiled with clang, trying to get a C++ exception thrown and caught by the MSVC-compiled code across a function in the clang-compiled code. My goal here is to isolate a small part of what needs to be done in a way that lends itself to tinkering. I think this might lead me to the