pr45055 tests a scheduling fix, but on targets that don't support
scheduling (like m32c-elf), gcc emits a warning that scheduling is not
supported.  This warning causes the test to fail.  How do we bypass
these types of test cases?  I don't see a suitable effective_target
for scheduling.

spawn -ignore SIGHUP /greed/dj/m32c/gcc/m32c-elf/gcc/xgcc
-B/greed/dj/m32c/gcc/m32c-elf/gcc/
/greed/dj/m32c/gcc/gcc/gcc/testsuite/gcc.dg/pr45055.c -O2 -ftracer
-fsched-pressure -funroll-loops -fschedule-insns -fcompare-debug
-DSTACK_SIZE=4096 -DNO_TRAMPOLINES -S -msim -mcpu=m16c -o pr45055.s

/greed/dj/m32c/gcc/gcc/gcc/testsuite/gcc.dg/pr45055.c:1:0: warning:
instruction scheduling not supported on this target machine [enabled
by default]

FAIL: gcc.dg/pr45055.c (test for excess errors)

Reply via email to