[Bug tree-optimization/55111] New: ICE: tree check: expected ssa_name, have integer_cst in live_on_edge, at tree-vrp.c:89

antoine.balestrat at gmail dot com gcc-bugzilla@gcc.gnu.org
Sun Oct 28 19:17:00 GMT 2012


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

             Bug #: 55111
           Summary: ICE: tree check: expected ssa_name, have integer_cst
                    in live_on_edge, at tree-vrp.c:89
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: antoine.balestrat@gmail.com


With GCC 4.8.0 as of 20121021, at -O2 and higher :

$ cat ssa.c
int a, b, c;
long d;
unsigned long *e;

int f(void)
{
    for(;; a++)
    {
        if(c)
        {
            for(b = d = 0; b < 1; b++)
                e = &d;

            --*e;

            if(d > 0)
                a = 0;

            return d;
        }
    }
}

$ xgcc -O2 -w ssa.c
ssa.c: In function ‘f’:
ssa.c:5:5: internal compiler error: tree check: expected ssa_name, have
integer_cst in live_on_edge, at tree-vrp.c:89
 int f(void)
     ^
linux-vdso.so.1: No such file or directory
0xa90b9a tree_check_failed(tree_node const*, char const*, int, char const*,
...)
    ../../srcdir/gcc/tree.c:8896
0xa7650d tree_check
    ../../srcdir/gcc/tree.h:3676
0xa7650d live_on_edge
    ../../srcdir/gcc/tree-vrp.c:89
0xa7ce9a register_edge_assert_for_2
    ../../srcdir/gcc/tree-vrp.c:4736
0xa7e4e0 register_edge_assert_for
    ../../srcdir/gcc/tree-vrp.c:5216
0xa81734 find_conditional_asserts
    ../../srcdir/gcc/tree-vrp.c:5304
0xa81734 find_assert_locations_1
    ../../srcdir/gcc/tree-vrp.c:5518
0xa88136 find_assert_locations
    ../../srcdir/gcc/tree-vrp.c:5658
0xa88136 insert_range_assertions
    ../../srcdir/gcc/tree-vrp.c:5846
0xa88136 execute_vrp
    ../../srcdir/gcc/tree-vrp.c:9156
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.



More information about the Gcc-bugs mailing list