search for: __llvm_personality_v0

...most exception implementations are based on (with a two phase unwind algorithm) -- which creates a problem for the debugger user. so, the question is will there be a specific recognizable "catch all types" type that can occur in the landingpad's catch list ? and will there be a __llvm_personality_v0 that is designed to do the right thing for this case. yes, I know this is a can-of-worms, it will break gcc compatibility, but then perhaps we can be the motivation for gnu folks to fix their implementation, be the leader rather than the follower.!. 4.b) it is not at all clear from your wr...

...alysis, it seems too error- > prone as __terminate() might be reachable for other reasons (not that I have come > up with such a scenario yet, but I think I might be able to), and this conclusion would > then be ambiguous). > > Even if support for the terminate option required a new __llvm_personality_v0 and > a new Unwind library function, I am still in favor of having and using it. But I suspect > that CodeGen can lower this into the same old MC branch to a block that only contains > __terminate() that we currently see in IR, and a new personality and Unwind > aren't necessary,...

...which would let debuggers interrupt or control unwinding without hooking libUnwind, short of requiring every single call to have an associated landing pad which the personality always lands at, even if there's nothing to do there. That will never, ever be acceptable. > and will there be a __llvm_personality_v0 that is designed to do the right thing for this case. > > yes, I know this is a can-of-worms, it will break gcc compatibility, but then perhaps we can be the > motivation for gnu folks to fix their implementation, be the leader rather than the follower.!. Using our own personality functi...