public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bart dot vanassche at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19808] miss a warning about uninitialized members in constructor
Date: Wed, 24 Feb 2010 19:10:00 -0000 [thread overview]
Message-ID: <20100224191041.12907.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19808-5329@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from bart dot vanassche at gmail dot com 2010-02-24 19:10 -------
(In reply to comment #9)
> I think there is no reasonable way to get reliable uninitialized variable
> warnings for incoming pointed-to memory. The only way we can warn here
> is by inlining the constructor into the caller to see either a static
> variable or the memory allocation.
Why would inlining the constructor be necessary ? Does this mean that it is not
possible to mark member variables as uninitialized in gcc ?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808
next prev parent reply other threads:[~2010-02-24 19:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19808-5329@http.gcc.gnu.org/bugzilla/>
2006-02-02 12:58 ` pinskia at gcc dot gnu dot org
2007-12-04 21:04 ` myselfhimself at free dot fr
2008-07-21 14:31 ` manu at gcc dot gnu dot org
2010-02-24 12:46 ` manu at gcc dot gnu dot org
2010-02-24 12:59 ` manu at gcc dot gnu dot org
2010-02-24 16:44 ` jason at gcc dot gnu dot org
2010-02-24 18:04 ` rguenth at gcc dot gnu dot org
2010-02-24 19:10 ` bart dot vanassche at gmail dot com [this message]
2010-02-24 19:45 ` manu at gcc dot gnu dot org
2010-02-24 20:13 ` jason at gcc dot gnu dot org
2010-02-24 20:15 ` manu at gcc dot gnu dot org
2010-02-24 20:22 ` rguenth at gcc dot gnu dot org
2010-02-24 20:30 ` manu at gcc dot gnu dot org
2010-02-24 20:44 ` jason at gcc dot gnu dot org
2010-02-24 20:45 ` jason at gcc dot gnu dot org
2010-02-25 7:01 ` bart dot vanassche at gmail dot com
2010-02-25 7:06 ` bart dot vanassche at gmail dot com
[not found] <bug-19808-4@http.gcc.gnu.org/bugzilla/>
2013-07-17 9:26 ` 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
2005-02-07 23:16 [Bug c++/19808] New: " adl at gnu dot org
2005-02-08 9:35 ` [Bug c++/19808] " bangerth at dealii dot org
2005-02-08 9:59 ` pinskia at gcc dot gnu 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=20100224191041.12907.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).