This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: C++ EH vs Forced Unwinding, Round 3


On Fri, 2003-05-02 at 14:10, Jason Merrill wrote:
> On Fri, 2 May 2003 13:48:55 -0700, Richard Henderson <rth@redhat.com> wrote:
> 
> > No, this isn't really sufficient.  You skipped over the bit where
> > it's non-negotiable that we retain control of the unwinding process
> > with the _Unwind_ForceUnwind hook.  
> 
> I think the real dispute here is over whether cancellation should use
> forced unwind, as Mark asked earlier in the discussion.
> 
> Does anyone disagree with always using my solution for longjmp_unwind?

I do not disagree; you try to unwind, if a catch clause does not
rethrow, call std::terminate, and you stop if and when you reach the
setjmp point.  That makes sense to me.

Thanks,

-- 
Mark Mitchell <mark@codesourcery.com>
CodeSourcery, LLC


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]