This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/81674] gcc cannot detect missing initialisers for fields in constructors
- From: "msebor at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 02 Feb 2018 00:22:38 +0000
- Subject: [Bug c++/81674] gcc cannot detect missing initialisers for fields in constructors
- Auto-submitted: auto-generated
- References: <bug-81674-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81674
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-02-02
CC| |msebor at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=19808
Ever confirmed|0 |1
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Bug 19808 is similar but not quite the same. It (and its duplicates) asks for
a warning when an uninitialized member is used to initialized another. This
one seems to be asking for a warning for members that are left uninitialized,
even when they are not used. This would be a noisier warning that
-Wuninitialized so it would probably need its own option, but I think it would
useful nonetheless.
It's likely that there already is a request like this one but I can't find it.
Let me confirm this in the meantime.