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++/58536] New: [c++1y] ICE with auto in constructor Date: Wed, 25 Sep 2013 21:14:00 -0000 [thread overview] Message-ID: <bug-58536-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58536 Bug ID: 58536 Summary: [c++1y] ICE with auto in constructor Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: reichelt at gcc dot gnu.org The following (valid, I think) code snippet (compiled with "-std=gnu++1y") triggers an ICE on trunk (4.9.0 20130922): ================ struct A { A(auto); }; A::A(auto) {} ================ bug.cc:6:10: internal compiler error: in poplevel_class, at cp/name-lookup.c:2928 A::A(auto) {} ^ 0x6f4834 poplevel_class() ../../gcc/gcc/cp/name-lookup.c:2928 0x5e9c88 popclass() ../../gcc/gcc/cp/class.c:7033 0x5ea10a pop_nested_class() ../../gcc/gcc/cp/class.c:7179 0x642cf9 cp_parser_direct_declarator ../../gcc/gcc/cp/parser.c:17213 0x642cf9 cp_parser_declarator ../../gcc/gcc/cp/parser.c:16690 0x649679 cp_parser_init_declarator ../../gcc/gcc/cp/parser.c:16258 0x64a32f cp_parser_simple_declaration ../../gcc/gcc/cp/parser.c:10986 0x64c190 cp_parser_block_declaration ../../gcc/gcc/cp/parser.c:10867 0x6551ae cp_parser_declaration ../../gcc/gcc/cp/parser.c:10764 0x653f0d cp_parser_declaration_seq_opt ../../gcc/gcc/cp/parser.c:10650 0x6557e6 cp_parser_translation_unit ../../gcc/gcc/cp/parser.c:3939 0x6557e6 c_parse_file() ../../gcc/gcc/cp/parser.c:28893 0x768164 c_common_parse_file() ../../gcc/gcc/c-family/c-opts.c:1046 Please submit a full bug report, [etc.]
next reply other threads:[~2013-09-25 21:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-25 21:14 reichelt at gcc dot gnu.org [this message] 2013-09-29 17:15 ` [Bug c++/58536] " daniel.kruegler at googlemail dot com 2013-09-29 20:41 ` reichelt at gcc dot gnu.org 2013-11-12 20:17 ` abutcher at gcc dot gnu.org 2013-11-13 6:46 ` reichelt 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-58536-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).