riscv
/
riscv-gnu-toolchain
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Browse Source

Add comments explaining why fortran tests fail (#272)

pull/273/head
Andrew Waterman 9 years ago
committed by GitHub
parent
1a74ccbe5e
commit
2a70a41448
1 changed files with 6 additions and 0 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 6
      test/gcc-linux/rv64imafdc-lp64d.log

6
test/gcc-linux/rv64imafdc-lp64d.log
View File

@ -23,18 +23,24 @@ build-gcc-linux-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c
build-gcc-linux-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 0" 2
build-gcc-linux-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 2" 1
build-gcc-linux-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile "Read tp_first_run: 3" 1
# ieee_1.F90 is a QEMU bug: https://github.com/riscv/riscv-qemu/issues/64
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_1.F90 -O0 execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_1.F90 -O1 execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_1.F90 -O2 execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_1.F90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_1.F90 -O3 -g execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_1.F90 -Os execution test
# ieee_8.f90 fails because ieee_support_halting(non-const-expr) correctly
# returns false, but ieee_support_halting(const-expr) incorrectly returns
# true. It looks like a huge pain to fix this, because we'd probably need
# to introduce a new target hook for IEEE 754 exception support.
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_8.f90 -O0 execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_8.f90 -O1 execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_8.f90 -O2 execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_8.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_8.f90 -O3 -g execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/ieee_8.f90 -Os execution test
# large_3.F90 appears to be the same QEMU bug as ieee_1.F90: https://github.com/riscv/riscv-qemu/issues/64
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/large_3.F90 -O0 execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/large_3.F90 -O1 execution test
build-gcc-linux-stage2/gcc/testsuite/gfortran/gfortran.sum:FAIL: gfortran.dg/ieee/large_3.F90 -O2 execution test

Write Preview
Loading…
Cancel
Save