Displaying 3 results from an estimated 3 matches for "3556234d".
Did you mean:
355234
2008 Jul 31
0
[LLVMdev] Unwinds Gone Wild
Hi,
> 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.
codegen doesn't know how to handle "unwind" on any target. You need
to call the libgcc unwinding routines directly (or indirectly by
2008 Jul 31
2
[LLVMdev] Unwinds Gone Wild
...ce if this was documented somewhere, although I understand the
difficulties in keeping documentation up-to-date.
>
> Ciao,
>
> Duncan.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080731/3556234d/attachment.html>
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() {