public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60804] New: Another CilkPlus ICE in gimplify_expr, at gimplify.c:8335 Date: Thu, 10 Apr 2014 04:51:00 -0000 [thread overview] Message-ID: <bug-60804-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60804 Bug ID: 60804 Summary: Another CilkPlus ICE in gimplify_expr, at gimplify.c:8335 Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: andi-gcc at firstfloor dot org Created attachment 32577 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32577&action=edit test case from csmith I hacked csmith to add some _Cilk_spawn keywords and let it run for a bit. The only new ICE that turned up was this (in various incarnations) Here's the unreduced file from csmith. x.c:178:35: internal compiler error: in gimplify_expr, at gimplify.c:8335 if ((safe_div_func_uint8_t_u_u(_Cilk_spawn func_4(((--(*l_9)) , g_10), (((( void*)0 != g_13) , (&g_14[1][0] == ((safe_add_func_uint32_t_u_u(g_14[1][0], (g_1 9 || (((*l_2079) = _Cilk_spawn func_20(((safe_rshift_func_uint16_t_u_s((~((*l_39 ) = ((safe_rshift_func_int16_t_s_u(((*l_37) = (safe_add_func_int8_t_s_s((_Cilk_s pawn func_28(g_31, g_32) <= g_19), 0x5FL))), 11)) , 0xC254L))), 5)) & g_19))) != (void*)0)))) , &g_33))) | l_2080), g_420[4][0][1], g_847), l_2080))) ^ 0x79bad0 gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_ba se**, bool (*)(tree_node*), int) ../../gcc/gcc/gimplify.c:8335 0x799d38 gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_ba se**, bool (*)(tree_node*), int) ../../gcc/gcc/gimplify.c:7715 0x7a0ed3 gimplify_call_expr ../../gcc/gcc/gimplify.c:2354 0x79b1fc gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_ba se**, bool (*)(tree_node*), int) ../../gcc/gcc/gimplify.c:7402 0x79aacc gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_ba ...
next reply other threads:[~2014-04-10 4:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-10 4:51 andi-gcc at firstfloor dot org [this message] 2014-04-10 10:54 ` [Bug c/60804] " jakub at gcc dot gnu.org 2014-04-10 14:53 ` andi-gcc at firstfloor dot org 2014-04-11 6:55 ` jakub at gcc dot gnu.org 2014-04-11 7:39 ` jakub at gcc dot gnu.org 2014-04-11 13:08 ` evstupac at gmail dot com 2014-04-11 13:10 ` mpolacek at gcc dot gnu.org 2014-04-11 14:15 ` jakub at gcc dot gnu.org 2014-04-11 20:24 ` andi-gcc at firstfloor dot org 2014-09-28 14:34 ` ak at gcc dot gnu.org 2014-09-28 14:38 ` ak at gcc dot gnu.org 2014-11-11 5:11 ` ak at gcc dot gnu.org 2014-11-11 17:56 ` andi-gcc at firstfloor dot 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-60804-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).