public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "piotr dot wyderski at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/44499] New: No default constructor available Date: Fri, 11 Jun 2010 09:10:00 -0000 [thread overview] Message-ID: <bug-44499-17090@http.gcc.gnu.org/bugzilla/> (raw) The following code: class C { }; class D : public C { }; const D g_d; fails to compile on trunk (rev. 160489) with the following message: $ g++ test.cpp test.cpp:11:9: error: uninitialized const 'g_d' [-fpermissive] test.cpp:6:11: note: 'const class D' has no user-provided default constructor -- Summary: No default constructor available Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: piotr dot wyderski at gmail dot com GCC build triplet: i686-pc-cygwin GCC host triplet: i686-pc-cygwin GCC target triplet: i686-pc-cygwin http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44499
next reply other threads:[~2010-06-11 9:10 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-11 9:10 piotr dot wyderski at gmail dot com [this message] 2010-06-11 9:26 ` [Bug c++/44499] " redi at gcc dot gnu dot org 2010-06-11 10:28 ` redi at gcc dot gnu dot org 2010-06-11 10:53 ` manu at gcc dot gnu dot org 2010-06-11 11:01 ` piotr dot wyderski at gmail dot com 2010-06-11 11:12 ` manu at gcc dot gnu dot org 2010-06-11 11:12 ` manu at gcc dot gnu dot org 2010-06-11 11:14 ` manu at gcc dot gnu dot org 2010-07-02 8:09 ` manu at gcc dot gnu dot org 2010-07-02 8:12 ` pluto at agmk dot net 2010-07-02 9:15 ` manu 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=bug-44499-17090@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).