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++/60052] New: [c++1y] ICE with auto as member function parameter Date: Tue, 04 Feb 2014 07:14:00 -0000 [thread overview] Message-ID: <bug-60052-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60052 Bug ID: 60052 Summary: [c++1y] ICE with auto as member function parameter 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 code snippet (compiled with "-std=c++1y") triggers an ICE on trunk: ================================== struct A { void foo(auto); }; void A::foo(auto) {} struct B { void bar(auto); }; ================================== bug.cc:10:11: internal compiler error: Segmentation fault void bar(auto); ^ 0xba9c8f crash_signal ../../gcc/gcc/toplev.c:337 0x6ce47b tree_check ../../gcc/gcc/tree.h:2708 0x6ce47b synthesize_implicit_template_parm ../../gcc/gcc/cp/parser.c:31950 0x6ce47b cp_parser_simple_type_specifier ../../gcc/gcc/cp/parser.c:14504 0x6abcdd cp_parser_type_specifier ../../gcc/gcc/cp/parser.c:14380 0x6c5400 cp_parser_decl_specifier_seq ../../gcc/gcc/cp/parser.c:11547 0x6c79c7 cp_parser_parameter_declaration ../../gcc/gcc/cp/parser.c:18432 0x6c8da1 cp_parser_parameter_declaration_list ../../gcc/gcc/cp/parser.c:18258 0x6c93f2 cp_parser_parameter_declaration_clause ../../gcc/gcc/cp/parser.c:18179 0x6bf3f0 cp_parser_direct_declarator ../../gcc/gcc/cp/parser.c:17072 0x6bf3f0 cp_parser_declarator ../../gcc/gcc/cp/parser.c:16943 0x6a890d cp_parser_member_declaration ../../gcc/gcc/cp/parser.c:20295 0x6abf74 cp_parser_member_specification_opt ../../gcc/gcc/cp/parser.c:19976 0x6abf74 cp_parser_class_specifier_1 ../../gcc/gcc/cp/parser.c:19210 0x6abf74 cp_parser_class_specifier ../../gcc/gcc/cp/parser.c:19437 0x6abf74 cp_parser_type_specifier ../../gcc/gcc/cp/parser.c:14302 0x6c5400 cp_parser_decl_specifier_seq ../../gcc/gcc/cp/parser.c:11547 0x6cbff9 cp_parser_simple_declaration ../../gcc/gcc/cp/parser.c:11137 0x6af4b3 cp_parser_block_declaration ../../gcc/gcc/cp/parser.c:11086 0x6d67b2 cp_parser_declaration ../../gcc/gcc/cp/parser.c:10983 Please submit a full bug report, [etc.]
next reply other threads:[~2014-02-04 7:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-04 7:14 reichelt at gcc dot gnu.org [this message] 2014-02-21 7:48 ` [Bug c++/60052] " abutcher at gcc dot gnu.org 2014-02-21 21:13 ` 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-60052-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).