public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53594] [C++11] Spurious -Wuninitialized warning for member with NSDMI Date: Wed, 06 Jun 2012 16:52:00 -0000 [thread overview] Message-ID: <bug-53594-4-bPPODySHr6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53594-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53594 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Summary|[C++11Spurious |[C++11] Spurious |-Wuninitialized warning for |-Wuninitialized warning for |member with NSDMI |member with NSDMI --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-06-06 16:52:00 UTC --- $ g++-4.7 -std=c++11 c.cc -c -Wuninitialized -c c.cc: In instantiation of 'class Range<int, 0>': c.cc:7:15: required from here c.cc:4:19: warning: non-static const member 'const int Range<int, 0>::min' in class without a constructor [-Wuninitialized] The test in class.c:check_bases_and_members doesn't appear to look for NSDMIs
next prev parent reply other threads:[~2012-06-06 16:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-06 16:50 [Bug c++/53594] New: [C++11Spurious " redi at gcc dot gnu.org 2012-06-06 16:52 ` redi at gcc dot gnu.org [this message] 2012-06-06 16:56 ` [Bug c++/53594] [C++11] Spurious " redi at gcc dot gnu.org 2012-06-11 7:58 ` pinskia at gcc dot gnu.org 2012-06-11 7:59 ` pinskia at gcc dot gnu.org 2012-06-11 8:58 ` jakub at gcc dot gnu.org 2012-06-11 9:29 ` vincenzo.innocente at cern dot ch 2012-06-25 6:48 ` jakub at gcc dot gnu.org 2012-06-25 6:55 ` jakub at gcc dot gnu.org 2012-06-25 6:55 ` jakub at gcc dot gnu.org 2012-06-25 6:58 ` jakub 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-53594-4-bPPODySHr6@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: 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).