search for: catchthrow

Displaying 6 results from an estimated 6 matches for "catchthrow".

2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...urious effect where if I JIT a function > that throws an exception and I use "call" to call it the throw fails > despite there being a "catch" clause on the stack. But if I use “invoke” it > works fine! > > If I call the function (@cc_invoke) that throws a “core::CatchThrow” > exception like this: > > call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) > ;; Comment out the next two lines and > ; to label %return0 unwind label %landing-pad1 > ;return0: > ret void > > landing-pad1:...
2015 Apr 09
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
Hi Christian, Andy's already covered the major points, but you could consider filing a bug at http://llvm.org/bugs too, especially if you've got a small test-case that demonstrates the issue. Exception handling hasn't been a priority in the past, but as more people adopt LLVM's JIT APIs I suspect it will get more attention, and bug reports will help us figure out what needs doing.
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...if I JIT a >> function that throws an exception and I use "call" to call it the throw >> fails despite there being a "catch" clause on the stack. But if I use >> “invoke” it works fine! >> >> If I call the function (@cc_invoke) that throws a “core::CatchThrow” >> exception like this: >> >> call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) >> ;; Comment out the next two lines and >> ; to label %return0 unwind label %landing-pad1 >> ;return0: >> ret voi...
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...ious effect where if I JIT a function that throws an exception and I use "call" to call it the throw fails despite there being a "catch" clause on the stack. But if I use “invoke” it works fine! >>> >>> If I call the function (@cc_invoke) that throws a “core::CatchThrow” exception like this: >>> call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) >>> ;; Comment out the next two lines and >>> ; to label %return0 unwind label %landing-pad1 >>> ;return0: >>> re...
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...e if I JIT a function that throws an exception and I use "call" to call it the throw fails despite there being a "catch" clause on the stack. But if I use “invoke” it works fine! >>>>> >>>>> If I call the function (@cc_invoke) that throws a “core::CatchThrow” exception like this: >>>>> call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) >>>>> ;; Comment out the next two lines and >>>>> ; to label %return0 unwind label %landing-pad1 >>>&g...
2015 Apr 12
2
[LLVMdev] Looking for advice on how to debug a problem with C++ style exception handling code that my compiler generates.
...IT a function that throws an exception and I use "call" to call it the throw fails despite there being a "catch" clause on the stack. But if I use “invoke” it works fine! >>>>>> >>>>>> If I call the function (@cc_invoke) that throws a “core::CatchThrow” exception like this: >>>>>> call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) >>>>>> ;; Comment out the next two lines and >>>>>> ; to label %return0 unwind label %landing-pad1 &g...