This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [v3] PATCH to libstdc++ for forced unwind handling (c++/28145)
On Thursday 03 of May 2007 16:21:01 Jason Merrill wrote:
> PaweÅ Sikora wrote:
> > On Thursday 03 of May 2007 08:35:46 Jason Merrill wrote:
> >> Tested x86_64-pc-linux-gnu. Any comments before I check it in?
> >>
> >> ! class __forced_unwind
> >> ! {
> >> ! virtual ~__forced_unwind() throw();
> >> ! virtual void __pure() = 0; // prevent catch by value
> >> ! };
> >
> > You can do abstract class much simplier:
> >
> > class __forced_unwind
> > {
> > virtual ~__forced_unwind() throw() = 0;
> > };
>
> Yes, but due to an oversight when we were designing the ABI, the
> destructor needs to be non-pure for it to control the output of the
> type_info.
i don't know the type info implementation details but if you need
the destructor body and vtable for __forced_unwind you can add
an empty destructor definition in library still having
pure class declaration without ugly __pure() method.