public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "l.lunak at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55203] No unused warning for variables of non-trivial types
Date: Sun, 04 Nov 2012 11:04:00 -0000 [thread overview]
Message-ID: <bug-55203-4-g8KcNRcJIk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55203-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55203
Lubos Lunak <l.lunak at suse dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #1 from Lubos Lunak <l.lunak at suse dot cz> 2012-11-04 11:04:01 UTC ---
As the compiler cannot tell for sure in some cases, such as the ctor calling an
external function, the only reasonable way of handling this I see is explicit
tagging of types for which there should be an unused warning if only ctor/dtor
are called for a variable. Here's my attempt at attribute warn_unused.
next prev parent reply other threads:[~2012-11-04 11:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 10:48 [Bug c++/55203] New: " l.lunak at suse dot cz
2012-11-04 11:04 ` l.lunak at suse dot cz [this message]
2012-11-04 11:05 ` [Bug c++/55203] " l.lunak at suse dot cz
2012-11-07 14:55 ` paolo.carlini at oracle dot com
2013-06-15 18:13 ` paolo.carlini at oracle dot com
2013-07-16 6:41 ` l.lunak at suse dot cz
2013-07-16 9:57 ` redi at gcc dot gnu.org
2013-07-16 9:58 ` redi at gcc dot gnu.org
2013-07-16 11:29 ` l.lunak at suse dot cz
2013-07-16 12:30 ` redi at gcc dot gnu.org
2021-09-15 15:51 ` msebor 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-55203-4-g8KcNRcJIk@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).