Re: [cxx-abi-dev] gcc unwind ABI change for forced unwind

[Cary Coutant <cary@xxxxxxxxxx>]

> Personally, I dislike the attempt to separate "cleanup" from 
> "finalization" (handle/catch). I don't like the idea of an exception 
> that can't be finalized, because it reduces the application's ability 
> to control behavior.
I didn't mean to imply that I liked this either, but it seemed a useful 
compromise given the unlikelihood that C++ will ever add try/finally.
I'm still not entirely comfortable with the idea of thread cancellation 
(and other forced unwinds) being a normal (catchable) C++ exception, 
but if consensus has been reached outside this list, and those on this 
list generally agree, I don't want to drag the discussion out any more.
What changes are needed in the C++ ABI document? Do we need to add 
anything in the base (C) ABI to cover thread cancellation and exit so 
that cleanups can be properly interleaved?
-cary