Displaying 3 results from an estimated 3 matches for "eh_selector".
Did you mean:
_selector
2011 Sep 22
1
[LLVMdev] UpgradeExceptionHandling
...utility which worked fine in my case.
However, ... as UpgradeExceptionHandling(...) will go away in 3.1, one should upgrade
their pre 3.0 exception handling code to the 3.0 system as soon as possible. The
new system is more concise, and therefore cleaner, as it merges in the old
llvm::Intrinsic::eh_selector, and llvm::Intrinsic::eh_exception intrinsics into one landpad
instruction. Also I'm not sure if use of UpgradeExceptionHandling(...) is an approved
approach so depending on it may be at one's own expense.
As I found the implementation of the UpgradeExceptionHandling(...) to be pretty coo...
2010 Jan 22
0
[LLVMdev] Exception handling question
2010/1/22 Garrison Venn <gvenn.cfe.dev at gmail.com>
> Yes. The issue here, as you pointed out, is that your personality function
> is not called at all.
> Even if you did nothing in the personality function, associated with the
> setup caused by
> llvm.eh.selector, but returned _URC_CONTINUE_UNWIND (8), it should still be
> called.
> Your results are acting like either
2010 Jan 22
6
[LLVMdev] Exception handling question
Yes. The issue here, as you pointed out, is that your personality function is not called at all.
Even if you did nothing in the personality function, associated with the setup caused by
llvm.eh.selector, but returned _URC_CONTINUE_UNWIND (8), it should still be called.
Your results are acting like either dwarf exception header info is not emitted (llvm::DwarfExceptionHandling = true;
not executed