https://llvm.org/bugs/show_bug.cgi?id=24185
Sanjoy Das <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |[email protected] Resolution|INVALID |--- --- Comment #3 from Sanjoy Das <[email protected]> --- After reading http://llvm.org/docs/ExceptionHandling.html, I think this bug merits re-opening. The doc says: * catch <type> @ExcType * This clause means that the landingpad block should be entered if the exception being thrown is of type @ExcType or a subtype of @ExcType. For C++, @ExcType is a pointer to the std::type_info object (an RTTI object) representing the C++ exception type. * If @ExcType is null, any exception matches, so the landingpad should always be entered. This is used for C++ catch-all blocks (“catch (...)”). * When this clause is matched, the selector value will be equal to the value returned by “@llvm.eh.typeid.for(i8* @ExcType)”. This will always be a positive value. The doc does not say that landing pads execute for every thrown exception. I could not find anything that says landingpads execute for any exception in the Itanium EH ABI either. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ LLVMbugs mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
