Displaying 2 results from an estimated 2 matches for "__llvm_cxxeh_throw".
2008 Sep 26
1
[LLVMdev] Unwinds Gone Wild
...like an epically nasty hack; totally
undocumented and platform-specific.
Maybe I'm misunderstanding the unwind instruction. The
http://llvm.org/pubs/2004-01-30-CGO-LLVM.pdf 2004 paper describes
exceptions in some detail. They use some front-end specific code for
allocating the exception (eg. __llvm_cxxeh_throw), but then call unwind to
actually unwind the stack.
Are you saying that you need to do something (like call cxa_throw) in*stead*
of calling unwind, or as well as calling unwind? In other words, if LLVM
didn't have this "bug", should Marc's code work fine, or is there still
somet...
2008 Jul 31
4
[LLVMdev] Unwinds Gone Wild
Can anyone tell me if invoke/unwind is stable in 2.3? I'm seeing some
really weird stuff -- unwinds are ending up in seemingly arbitrary places...
definitely not inside the caller's unwind block My target is x86.
As a simple test, I tried to compile the following code and I got a
segmentation fault. It looks good to me. Can someone help me out or is
this a bug?
define i32 @foo() {