On 1/11/19 1:36 PM, Tobias Burnus wrote:
Dear Jason, dear all,
Jason Merrill wrote on 5 Dec 2018:
You can get at the destructor with CLASSTYPE_DESTRUCTOR rather than walking
through TYPE_FIELDS. I'd also check DECL_DEFAULTED_IN_CLASS_P.
I'd also do this in maybe_emit_vtables rather than here,
Dear Jason, dear all,
Jason Merrill wrote on 5 Dec 2018:
> You can get at the destructor with CLASSTYPE_DESTRUCTOR rather than walking
> through TYPE_FIELDS. I'd also check DECL_DEFAULTED_IN_CLASS_P.
> I'd also do this in maybe_emit_vtables rather than here, so that it only
> happens once per
On 11/21/18 7:19 AM, Tobias Burnus wrote:
Hello all,
if a class contains any 'virtual ... = 0', it's an abstract class and for an
abstract class, the destructor not added to the vtable.
For a normal
virtual ~class() { }
that's not a problem as the class::~class() destructor will be
On Wed, Nov 28, 2018 at 09:35:53PM +0100, Tobias Burnus wrote:
> On the 25th November 2018, schrieb Tobias Burnus wrote:
> > On 21 November 2018, Tobias Burnus wrote:
> > > Hello all,
> > >
> > > if a class contains any 'virtual ... = 0', it's an abstract class
> > > and for an
> > > abstract
On the 25th November 2018, schrieb Tobias Burnus wrote:
On 21 November 2018, Tobias Burnus wrote:
Hello all,
if a class contains any 'virtual ... = 0', it's an abstract class and
for an
abstract class, the destructor not added to the vtable.
For a normal
virtual ~class() { }
that's not
On 21 November 2018, Tobias Burnus wrote:
Hello all,
if a class contains any 'virtual ... = 0', it's an abstract class and for an
abstract class, the destructor not added to the vtable.
For a normal
virtual ~class() { }
that's not a problem as the class::~class() destructor will be
Hello all,
if a class contains any 'virtual ... = 0', it's an abstract class and for an
abstract class, the destructor not added to the vtable.
For a normal
virtual ~class() { }
that's not a problem as the class::~class() destructor will be generated during
the parsing of the function.
But
