public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "z0sh at sogetthis dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/49669] New: Compiler crashes with "internal compiler error: in perform_member_init, at cp/init.c:530" Date: Thu, 07 Jul 2011 11:19:00 -0000 [thread overview] Message-ID: <bug-49669-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49669 Summary: Compiler crashes with "internal compiler error: in perform_member_init, at cp/init.c:530" Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: z0sh@sogetthis.com Host: x86 Target: x86 Build: x86 Compile this with "g++ -c x.cpp -std=c++0x": --- BEGIN FILE x.cpp --- struct Foo { explicit Foo(int) { } }; struct Goo { Goo() : x(Foo(4), Foo(5)) { } Foo x[2]; }; --- END FILE --- The compiler (GCC 4.6.0) crashes with this message: x.cpp: In constructor ‘Goo::Goo()’: x.cpp:2:38: internal compiler error: in perform_member_init, at cp/init.c:530
next reply other threads:[~2011-07-07 11:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-07 11:19 z0sh at sogetthis dot com [this message] 2011-07-07 11:27 ` [Bug c++/49669] [4.6/4.7 Regression] [C++0x] " redi at gcc dot gnu.org 2011-07-07 11:50 ` z0sh at sogetthis dot com 2011-07-07 12:13 ` redi at gcc dot gnu.org 2011-07-07 13:19 ` rguenth at gcc dot gnu.org 2011-07-07 16:10 ` z0sh at sogetthis dot com 2011-07-07 16:40 ` redi at gcc dot gnu.org 2011-08-01 14:55 ` rguenth at gcc dot gnu.org 2011-08-05 21:22 ` jason at gcc dot gnu.org 2011-08-06 4:37 ` jason at gcc dot gnu.org 2011-08-06 4:39 ` jason at gcc dot gnu.org 2011-08-06 8:54 ` paolo.carlini at oracle dot com
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-49669-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).