public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jwakely dot gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors Date: Thu, 03 Jun 2010 11:25:00 -0000 [thread overview] Message-ID: <20100603112442.27629.qmail@sourceware.org> (raw) In-Reply-To: <bug-2972-381@http.gcc.gnu.org/bugzilla/> ------- Comment #14 from jwakely dot gcc at gmail dot com 2010-06-03 11:24 ------- Created an attachment (id=20817) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20817&action=view) better -Wmeminit patch This version ignores empty classes and checks for a nontrivial default ctor instead of layout_pod_type. This patch doesn't enable the warning unless explicity requested. I realise that this warning is about enforcing style ("members should be initialised in the mem-initializer-list not in the ctor body") but that's ok because it's my preferred style, I just don't want the compiler to enforce other people's preferred style ;) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972
next prev parent reply other threads:[~2010-06-03 11:25 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-2972-381@http.gcc.gnu.org/bugzilla/> 2006-01-22 3:43 ` gdr at gcc dot gnu dot org 2008-09-10 15:31 ` bangerth at dealii dot org 2010-02-24 13:05 ` manu at gcc dot gnu dot org 2010-06-03 1:14 ` redi at gcc dot gnu dot org 2010-06-03 8:48 ` manu at gcc dot gnu dot org 2010-06-03 9:18 ` jwakely dot gcc at gmail dot com 2010-06-03 9:28 ` jwakely dot gcc at gmail dot com 2010-06-03 10:16 ` paolo dot carlini at oracle dot com 2010-06-03 11:25 ` jwakely dot gcc at gmail dot com [this message] [not found] <bug-2972-4@http.gcc.gnu.org/bugzilla/> 2010-12-03 19:07 ` redi at gcc dot gnu.org 2011-11-07 22:00 ` redi at gcc dot gnu.org 2012-08-21 17:21 ` paolo.carlini at oracle dot com 2012-08-21 17:27 ` redi at gcc dot gnu.org 2012-08-21 17:55 ` paolo.carlini at oracle dot com 2014-09-29 14:54 ` manu at gcc dot gnu.org 2021-11-19 3:54 ` mpolacek at gcc dot gnu.org [not found] <20010527045600.2972.pere@hungry.com> 2003-08-04 0:41 ` pinskia at physics dot uc dot edu 2004-01-07 3:35 ` eric-gcc at omnifarious 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=20100603112442.27629.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: linkBe 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).