3 Commits

Author	SHA1	Message	Date
John McCall	ffe4630f3d	When re-raising an exception after a cleanup, we need to call _Unwind_Resume_or_Rethrow ... instead of _Unwind_Resume. With SJLJ exceptions, this is spelled "_Unwind_SjLj_Resume_or_Rethrow", not "_Unwind_SjLj_Resume", which has significantly different semantics. We should actually never be generating a call to _Unwind_SjLj_Resume directly; even if we were generating true cleanups (which we aren't because of the horrible hack), we should be calling __cxa_end_cleanup() on ARM. I haven't implemented this because there's little point as long as the HH is present. I believe this fixes <rdar://problem/8281377>. llvm-svn: 110851	2010-08-11 20:59:53 +00:00
John McCall	2b7fc3828e	Teach IR generation how to lazily emit cleanups. This has a lot of advantages, ... mostly in avoiding unnecessary work at compile time but also in producing more sensible block orderings. Move the destructor cleanups for local variables over to use lazy cleanups. Eventually all cleanups will do this; for now we have some awkward code duplication. Tell IR generation just to never produce landing pads in -fno-exceptions. This is a much more comprehensive solution to a problem which previously was half-solved by checks in most cleanup-generation spots. llvm-svn: 108270	2010-07-13 20:32:21 +00:00
Daniel Dunbar	3241d400c8	Switch to using -fsjlj-exceptions instead of hard-coding it. Notably, this fixes ... calls to the UnwindResumeOrRethrow function for C++/Obj-C exception handling, for Darwin ARM. llvm-svn: 95787	2010-02-10 18:49:11 +00:00