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++/60250] New: [4.9 Regression] [c++1y] ICE using lambda for array size Date: Mon, 17 Feb 2014 21:27:00 -0000 [thread overview] Message-ID: <bug-60250-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60250 Bug ID: 60250 Summary: [4.9 Regression] [c++1y] ICE using lambda for array size Product: gcc Version: 4.9.0 Status: UNCONFIRMED Keywords: ice-on-valid-code 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. The code compiles fine, if it is compiled with "-std=c++11". ==================================== template<typename> void foo() { typedef int T[ ([](){ return 1; }()) ]; } ==================================== bug.cc: In function 'void foo()': bug.cc:3:40: internal compiler error: Segmentation fault typedef int T[ ([](){ return 1; }()) ]; ^ 0xba529f crash_signal ../../gcc/gcc/toplev.c:337 0x7422dd potential_constant_expression_1 ../../gcc/gcc/cp/semantics.c:10140 0x741680 potential_constant_expression_1 ../../gcc/gcc/cp/semantics.c:10495 0x74d0dd array_of_runtime_bound_p(tree_node*) ../../gcc/gcc/cp/tree.c:892 0x5e9656 grokdeclarator(cp_declarator const*, cp_decl_specifier_seq*, decl_context, int, tree_node**) ../../gcc/gcc/cp/decl.c:10174 0x5edc24 start_decl(cp_declarator const*, cp_decl_specifier_seq*, int, tree_node*, tree_node*, tree_node**) ../../gcc/gcc/cp/decl.c:4508 0x6c7e8e cp_parser_init_declarator ../../gcc/gcc/cp/parser.c:16680 0x6c9919 cp_parser_simple_declaration ../../gcc/gcc/cp/parser.c:11205 0x6acc03 cp_parser_block_declaration ../../gcc/gcc/cp/parser.c:11086 0x6add21 cp_parser_declaration_statement ../../gcc/gcc/cp/parser.c:10733 0x6ae36b cp_parser_statement ../../gcc/gcc/cp/parser.c:9467 0x6af159 cp_parser_statement_seq_opt ../../gcc/gcc/cp/parser.c:9745 0x6af2c6 cp_parser_compound_statement ../../gcc/gcc/cp/parser.c:9699 0x6c349b cp_parser_function_body ../../gcc/gcc/cp/parser.c:18641 0x6c349b cp_parser_ctor_initializer_opt_and_function_body ../../gcc/gcc/cp/parser.c:18677 0x6c77e2 cp_parser_function_definition_after_declarator ../../gcc/gcc/cp/parser.c:22792 0x6c8681 cp_parser_function_definition_from_specifiers_and_declarator ../../gcc/gcc/cp/parser.c:22704 0x6c8681 cp_parser_init_declarator ../../gcc/gcc/cp/parser.c:16585 0x6c8a1a cp_parser_single_declaration ../../gcc/gcc/cp/parser.c:23113 0x6c8d04 cp_parser_template_declaration_after_export ../../gcc/gcc/cp/parser.c:22915 Please submit a full bug report, [etc.]
next reply other threads:[~2014-02-17 21:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-17 21:27 reichelt at gcc dot gnu.org [this message] 2014-02-17 21:27 ` [Bug c++/60250] " reichelt at gcc dot gnu.org 2014-02-18 9:25 ` rguenth at gcc dot gnu.org 2014-02-21 4:47 ` jason at gcc dot gnu.org 2014-02-21 4:48 ` jason at gcc dot gnu.org 2014-02-21 14:02 ` jason at gcc dot gnu.org 2014-02-21 14:31 ` jakub 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-60250-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).