public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjagasia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/38559] [graphite] ICE :in build2_stat, at tree.c:3293 Date: Mon, 22 Dec 2008 19:42:00 -0000 [thread overview] Message-ID: <20081222194119.16699.qmail@sourceware.org> (raw) In-Reply-To: <bug-38559-16682@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from hjagasia at gcc dot gnu dot org 2008-12-22 19:41 ------- For the clast_stmt below: if (midend_8 >= mid_10+1) { for (s_3=0;s_3<=min(midend_8-mid_10-1,63);s_3++) { S5(0,s_3) ; } } graphite gets into translate_clast:stmt_guard->graphite_create_new_guard->graphite_create_guard_cond_expr->graphite_translate_clast_equation->clast_to_gcc_expression Finally graphite calls fold_build2 (PLUS_EXPR, type, tl, tr); which in turn calls build2_stat (code, type, op0, op1, PASS_MEM_STAT); Finally for the RHS of the clast guard equation "if (midend_8 >= mid_10+1)" the following code is invoked: if ((code == MINUS_EXPR || code == PLUS_EXPR || code == MULT_EXPR) && arg0 && arg1 && tt && POINTER_TYPE_P (tt)) gcc_assert (TREE_CODE (arg0) == INTEGER_CST || TREE_CODE (arg1) == INTEGER_CST); For the RHS, "mid_10+1", the TREE_CODE of "mid_10" is SSA_NAME and that of "1" is INTEGER_CST. Hence the gcc_assert raises an assertion. -- hjagasia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2008-12-22 19:41:18 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38559
next prev parent reply other threads:[~2008-12-22 19:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-17 23:24 [Bug middle-end/38559] New: " mitul dot thakkar at amd dot com 2008-12-17 23:25 ` [Bug middle-end/38559] " mitul dot thakkar at amd dot com 2008-12-22 19:42 ` hjagasia at gcc dot gnu dot org [this message] 2009-01-08 1:32 ` spop at gcc dot gnu dot org 2009-01-08 1:37 ` spop at gcc dot gnu dot org 2009-01-08 14:15 ` spop at gcc dot gnu 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=20081222194119.16699.qmail@sourceware.org \ --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).