public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53629] New: [c++11] spurious uninitialized warning in case of "non-static data member initializers".
Date: Mon, 11 Jun 2012 07:44:00 -0000	[thread overview]
Message-ID: <bug-53629-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53629

             Bug #: 53629
           Summary: [c++11] spurious uninitialized warning in case of
                    "non-static data member initializers".
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: vincenzo.innocente@cern.ch


in case of non-static data member initializers. such as

struct MyConfig_Foo {
  const int i=3;
  const float f=4.14f;
};

one gets

c++ -O2 -std=gnu++11 Config11.cpp  -Wall
Config11.cpp:21:15: warning: non-static const member ‘const int
MyConfig_Foo::i’ in class without a constructor [-Wuninitialized]
   const int i=3;
               ^
Config11.cpp:22:17: warning: non-static const member ‘const float
MyConfig_Foo::f’ in class without a constructor [-Wuninitialized]
   const float f=4.14f;
                 ^

which I find incorrect.


             reply	other threads:[~2012-06-11  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  7:44 vincenzo.innocente at cern dot ch [this message]
2012-06-11  7:57 ` [Bug c++/53629] " pinskia 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-53629-4@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).