public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fuscated at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58114] allow turning the warning about deleting a pointer of incomplete type into an error
Date: Wed, 16 Apr 2014 15:28:00 -0000 [thread overview]
Message-ID: <bug-58114-4-0Qc2HoNFsR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58114-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58114
Teodor Petrov <fuscated at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fuscated at gmail dot com
--- Comment #1 from Teodor Petrov <fuscated at gmail dot com> ---
This option is very important, because this warning allowed us to fix one
serious leak in our application. And to prevent this problem to reappear in the
future we want to force this warning to be error, but unfortunately we are not
able when building with GCC.
All other compilers we use have this feature. And btw in clang the option is
named -Wdelete-incomplete, so you can reuse it to minimize the difference
between the compilers.
BTW: Do someone has an explanation why this is allowed in the standard?
next prev parent reply other threads:[~2014-04-16 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 17:01 [Bug c++/58114] New: " tilman.vogel at web dot de
2014-04-16 15:28 ` fuscated at gmail dot com [this message]
2014-04-16 16:39 ` [Bug c++/58114] " redi at gcc dot gnu.org
2014-04-16 16:42 ` redi at gcc dot gnu.org
2014-04-17 16:27 ` fuscated at gmail dot com
2014-04-17 16:38 ` 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-58114-4-0Qc2HoNFsR@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).