public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "grosser at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37851] [graphite] ICE in expand_scalar_variables_expr, at graphite.c:3617
Date: Thu, 23 Oct 2008 20:11:00 -0000	[thread overview]
Message-ID: <20081023200952.27649.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37851-11725@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from grosser at gcc dot gnu dot org  2008-10-23 20:09 -------
It seems we do not have implemented all cases in expand_scalar_variables_expr()

Backtrace for "f951 -O2 -fgraphite-identity".

#1  0x081f3461 in fancy_abort (file=Could not find the frame base for
"fancy_abort".
) at ../../../git/gcc/diagnostic.c:712
#2  0x08a11e58 in expand_scalar_variables_expr (type=0x290a42d8,
op0=0x290d09b0, code=COMPONENT_REF, 
    op1=0x0, gbb=0x8e32fa0, scop=0x8e0df10, old_loop_father=0x29140160)
    at ../../../git/gcc/graphite.c:3617
#3  0x08a11e37 in expand_scalar_variables_expr (type=0x290a42d8,
op0=0x29131738, code=SSA_NAME, 
    op1=0x0, gbb=0x8e32fa0, scop=0x8e0df10, old_loop_father=0x29140160)
    at ../../../git/gcc/graphite.c:3612
#4  0x08a11ef4 in expand_scalar_variables_stmt (stmt=0x291283c0, gbb=0x8e32fa0,
scop=0x8e0df10, 
    old_loop_father=0x29140160) at ../../../git/gcc/graphite.c:3639
#5  0x08a12083 in expand_scalar_variables (gbb=0x8e32fa0, scop=0x8e0df10,
old_loop_father=0x29140160)
    at ../../../git/gcc/graphite.c:3666
#6  0x08a125bb in translate_clast (scop=0x8e0df10, context_loop=0x291331b8,
stmt=0x8ed2450, 
    next_e=0x29143938, ivstack=0xbfbfe8c0) at ../../../git/gcc/graphite.c:3791
#7  0x08a128bd in translate_clast (scop=0x8e0df10, context_loop=0x291331b8,
stmt=0x8e9c540, 
    next_e=0x29135d70, ivstack=0xbfbfe8c0) at ../../../git/gcc/graphite.c:3843
#8  0x08a1253d in translate_clast (scop=0x8e0df10, context_loop=0x291331b8,
stmt=0x8eb1ff0, 
    next_e=0x29135d70, ivstack=0xbfbfe8c0) at ../../../git/gcc/graphite.c:3777
#9  0x08a147b2 in gloog (scop=0x8e0df10, stmt=0x8eb1ff0) at
../../../git/gcc/graphite.c:4366

Here we miss: COMPONENT_REF


-- 

grosser at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |grosser at gcc dot gnu dot
                   |dot org                     |org
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2008-10-22 20:05:58         |2008-10-23 20:09:51
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37851


  parent reply	other threads:[~2008-10-23 20:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 15:00 [Bug middle-end/37851] New: " dwarak dot rajagopal at amd dot com
2008-10-16 15:01 ` [Bug middle-end/37851] " dwarak dot rajagopal at amd dot com
2008-10-22 20:07 ` grosser at gcc dot gnu dot org
2008-10-23 20:11 ` grosser at gcc dot gnu dot org [this message]
2008-10-23 20:12 ` grosser at gcc dot gnu dot org
2008-11-07 15:19 ` howarth at nitro dot med dot uc dot edu
2008-11-07 15:26 ` howarth at nitro dot med dot uc dot edu
2008-11-27 17:13 ` grosser at gcc dot gnu dot org
2008-12-03 20:55 ` 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=20081023200952.27649.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: link
Be 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).