On Mon, Sep 28, 2015 at 3:48 PM, Sebastian Paul Pop <s....@samsung.com> wrote: > I fixed this in a follow-up patch. >
Now I got https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67754 FAIL: gcc.dg/graphite/interchange-10.c execution test FAIL: gcc.dg/graphite/interchange-11.c execution test FAIL: gcc.dg/graphite/interchange-1.c execution test FAIL: gcc.dg/graphite/interchange-3.c execution test FAIL: gcc.dg/graphite/interchange-4.c execution test FAIL: gcc.dg/graphite/interchange-7.c execution test FAIL: gcc.dg/graphite/pr46185.c execution test FAIL: gcc.dg/graphite/uns-block-1.c execution test FAIL: gcc.dg/graphite/uns-interchange-12.c execution test FAIL: gcc.dg/graphite/uns-interchange-14.c execution test FAIL: gcc.dg/graphite/uns-interchange-15.c execution test FAIL: gcc.dg/graphite/uns-interchange-9.c execution test FAIL: gcc.dg/graphite/uns-interchange-mvt.c execution test FAIL: gfortran.dg/graphite/block-1.f90 -O (internal compiler error) FAIL: gfortran.dg/graphite/block-1.f90 -O (test for excess errors) on Linux/x86 with ISL 0.14. -- H.J.
