public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "irving at cs dot stanford dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/18016] Warn about member variables initialized with itself
Date: Fri, 27 Apr 2007 15:45:00 -0000 [thread overview]
Message-ID: <20070427154518.7142.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18016-4042@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from irving at cs dot stanford dot edu 2007-04-27 16:45 -------
Is there any chance of activity on this bug?
It would be wonderful to have a warning for this
case, since these bugs can be extremely annoying to find.
If the infrastructure supports it, the ideal way to resolve this might
be to manually mark all fields of this uninitialized on entry to each
constructor. If that's impossible because the dataflow is run only on
top level variables, just checking for occurences of :a(a) would help
a lot.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18016
next parent reply other threads:[~2007-04-27 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18016-4042@http.gcc.gnu.org/bugzilla/>
2007-04-27 15:45 ` irving at cs dot stanford dot edu [this message]
2010-02-21 19:17 ` manu at gcc dot gnu dot org
[not found] <bug-18016-4@http.gcc.gnu.org/bugzilla/>
2010-12-16 16:05 ` redi at gcc dot gnu.org
2010-12-21 15:28 ` redi at gcc dot gnu.org
2010-12-21 17:20 ` redi at gcc dot gnu.org
2010-12-22 9:18 ` manu at gcc dot gnu.org
2010-12-22 14:40 ` redi at gcc dot gnu.org
2011-05-23 8:39 ` redi at gcc dot gnu.org
2011-05-23 8:52 ` redi at gcc dot gnu.org
2011-06-27 18:07 ` ejb at ql dot org
2011-12-13 19:59 ` redi at gcc dot gnu.org
2012-11-14 11:41 ` redi at gcc dot gnu.org
2004-10-15 16:45 [Bug c++/18016] New: -Winit-self misses member variables initialized after : in ctor ejb at ql dot org
2004-10-15 17:05 ` [Bug c++/18016] Warn about member variables initialized with itself pinskia at gcc dot gnu dot org
2004-10-28 3:35 ` giovannibajo at libero dot it
2004-10-28 13:08 ` bangerth at dealii dot 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=20070427154518.7142.qmail@sourceware.org \
--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).