public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19808] miss a warning about uninitialized member usage in member initializer list in constructor
Date: Fri, 19 Nov 2021 03:54:15 +0000 [thread overview]
Message-ID: <bug-19808-4-xU4ncq53F2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-19808-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #51 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
At last, implemented.
next prev parent reply other threads:[~2021-11-19 3:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19808-4@http.gcc.gnu.org/bugzilla/>
2013-07-17 9:26 ` [Bug c++/19808] miss a warning about uninitialized members " redi at gcc dot gnu.org
2014-09-27 20:29 ` manu at gcc dot gnu.org
2014-09-29 13:06 ` jason at gcc dot gnu.org
2014-09-29 14:35 ` manu at gcc dot gnu.org
2014-11-15 23:11 ` [Bug c++/19808] miss a warning about uninitialized member usage in member initializer list " anthony.brandon at gmail dot com
2014-11-16 19:14 ` anthony.brandon at gmail dot com
2020-10-21 23:28 ` mpolacek at gcc dot gnu.org
2020-11-12 15:07 ` mpolacek at gcc dot gnu.org
2020-11-13 3:07 ` mpolacek at gcc dot gnu.org
2021-11-05 23:33 ` mpolacek at gcc dot gnu.org
2021-11-19 3:38 ` cvs-commit at gcc dot gnu.org
2021-11-19 3:54 ` mpolacek at gcc dot gnu.org [this message]
2021-11-19 9:09 ` dcb314 at hotmail dot com
2021-11-19 11:00 ` dcb314 at hotmail dot com
2021-11-19 11:09 ` redi at gcc dot gnu.org
2021-11-19 16:57 ` mpolacek at gcc dot gnu.org
2021-11-23 20:02 ` cvs-commit 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-19808-4-xU4ncq53F2@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).