Displaying 2 results from an estimated 2 matches for "tp18747589p19683007".
2008 Sep 26
1
[LLVMdev] Unwinds Gone Wild
...not followed by a ret instruction, where an empty
statement would not).
In the mean time, can anyone suggest a fix for Marc's dummy example which
works in the current version of LLVM (even if it's platform specific)?
--
View this message in context: http://www.nabble.com/Unwinds-Gone-Wild-tp18747589p19683007.html
Sent from the LLVM - Dev mailing list archive at Nabble.com.
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() {