public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64399] g++ does not diagnose when upcasting owning pointer (e.g. unique_ptr) with non-virtual destructor
Date: Wed, 24 Dec 2014 10:36:00 -0000 [thread overview]
Message-ID: <bug-64399-4-JhGijLejm2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64399-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64399
--- Comment #6 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> It might be valid with a custom deleter, but the example shown has undefined
> behaviour.
When the derived class does not add any member or redefine any important
functionality, it is not an uncommon technique to call the base class
destructor on a derived class. It might pedantically be illegal, but it is
useful, and I believe some people would like to avoid the warning when the two
destructors are equivalent.
next prev parent reply other threads:[~2014-12-24 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 22:58 [Bug libstdc++/64399] New: " mw_triad at users dot sourceforge.net
2014-12-23 23:33 ` [Bug libstdc++/64399] " redi at gcc dot gnu.org
2014-12-23 23:37 ` mw_triad at users dot sourceforge.net
2014-12-24 1:37 ` thiago at kde dot org
2014-12-24 8:59 ` redi at gcc dot gnu.org
2014-12-24 9:01 ` redi at gcc dot gnu.org
2014-12-24 10:36 ` glisse at gcc dot gnu.org [this message]
2014-12-24 16:59 ` mw_triad at users dot sourceforge.net
2021-08-31 18:20 ` redi at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-64399-4-JhGijLejm2@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).