public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51633] New: [c++0x] [4.6/4.7 Regression] ICE with invalid constexpr constructor Date: Tue, 20 Dec 2011 08:04:00 -0000 [thread overview] Message-ID: <bug-51633-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51633 Bug #: 51633 Summary: [c++0x] [4.6/4.7 Regression] ICE with invalid constexpr constructor Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: reichelt@gcc.gnu.org The following invalid code snippet triggers an ICE since GCC 4.6.0: ========================== struct A { ~A(); }; struct B { A a; constexpr B() {} }; ========================== bug.cc: In constructor 'constexpr B::B()': bug.cc:9:18: internal compiler error: in build_constexpr_constructor_member_initializers, at cp/semantics.c:5908 Please submit a full bug report, [etc.] A slightly different code snippet triggers an ICE in a different place: ========================== struct A { constexpr A() {} ~A(); }; struct B { A a; constexpr B() { return; } }; ========================== bug.cc: In constructor 'constexpr B::B()': bug.cc:10:27: internal compiler error: in build_data_member_initialization, at cp/semantics.c:5782 Please submit a full bug report, [etc.] This looks related to PR51612 where the ICE happens in the same place.
next reply other threads:[~2011-12-20 8:04 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-20 8:04 reichelt at gcc dot gnu.org [this message] 2011-12-20 8:22 ` [Bug c++/51633] " reichelt at gcc dot gnu.org 2011-12-20 10:39 ` paolo.carlini at oracle dot com 2011-12-30 6:31 ` pinskia at gcc dot gnu.org 2012-01-01 13:54 ` paolo.carlini at oracle dot com 2012-01-04 13:50 ` rguenth at gcc dot gnu.org 2012-01-09 18:41 ` dodji at gcc dot gnu.org 2012-01-11 13:23 ` dodji at gcc dot gnu.org 2012-01-11 13:54 ` jason at gcc dot gnu.org 2012-01-12 23:30 ` dodji at gcc dot gnu.org 2012-01-12 23:34 ` dodji 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-51633-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: 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).