| Message ID | CAJnFk2f437LChYYJcsgCdAA8VXcTR_SzD5MdubvZbNPGGuC4sQ@mail.gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | [10,RFC] Fix PR testsuite/90113 | expand |
Hi Roman, > FAIL: gfortran.dg/inline_matmul_1.f90 scan-tree-dump-times optimized > "_gfortran_matmul" 0 With matmul, there are three versions you can get: The library version (called as _gfortran_matmul), the inline version or a direct call to the corresponding BLAS routine. Which one is called, and if there is a run-time selection between them, depends on -O and some other options. You'll need to look at the test case in detail. Regards Thomas
diff --git a/gcc/testsuite/gfortran.dg/dg.exp b/gcc/testsuite/gfortran.dg/dg.exp --- a/gcc/testsuite/gfortran.dg/dg.exp +++ b/gcc/testsuite/gfortran.dg/dg.exp @@ -54,10 +54,10 @@ proc dg-compile-aux-modules { args } { } # Main loop. -gfortran-dg-runtest [lsort \ +dg-runtest [lsort \ [glob -nocomplain $srcdir/$subdir/*.\[fF\]{,90,95,03,08} ] ] "" $DEFAULT_FFLAGS -gfortran-dg-runtest [lsort \ +dg-runtest [lsort \ [glob -nocomplain $srcdir/$subdir/g77/*.\[fF\] ] ] "" $DEFAULT_FFLAGS
Hello Two weeks ago I posted https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90113 We have some unnecessary torture runs for gfortran.dg tests. Full description inside PR. Regtested r270624 trunk on x86_64: Unpatched: === gfortran tests === Running target unix === gfortran Summary === # of expected passes 50246 # of expected failures 188 # of unsupported tests 80 Patched: === gfortran tests === Running target unix FAIL: gfortran.dg/class_45b.f03 (test for excess errors) FAIL: gfortran.dg/inline_matmul_1.f90 scan-tree-dump-times optimized "_gfortran_matmul" 0 FAIL: gfortran.dg/iso_fortran_env_3.f90 (test for excess errors) UNRESOLVED: gfortran.dg/iso_fortran_env_3.f90 compilation failed to produce executable FAIL: gfortran.dg/iso_fortran_env_5.f90 (test for excess errors) UNRESOLVED: gfortran.dg/iso_fortran_env_5.f90 scan-tree-dump-times original "_gfortran_stop" 0 FAIL: gfortran.dg/iso_fortran_env_6.f90 (test for errors, line 24) FAIL: gfortran.dg/iso_fortran_env_6.f90 (test for errors, line 29) FAIL: gfortran.dg/iso_fortran_env_6.f90 (test for errors, line 34) FAIL: gfortran.dg/iso_fortran_env_6.f90 (test for excess errors) FAIL: gfortran.dg/iso_fortran_env_7.f90 (test for excess errors) FAIL: gfortran.dg/pr67140.f90 (test for excess errors) UNRESOLVED: gfortran.dg/pr67140.f90 compilation failed to produce executable FAIL: gfortran.dg/pr71649.f90 (test for errors, line 4) FAIL: gfortran.dg/pr71649.f90 (test for excess errors) FAIL: gfortran.dg/proc_ptr_comp_6.f90 (test for excess errors) UNRESOLVED: gfortran.dg/proc_ptr_comp_6.f90 compilation failed to produce executable FAIL: gfortran.dg/quad_1.f90 (test for excess errors) FAIL: gfortran.dg/quad_3.f90 (test for excess errors) UNRESOLVED: gfortran.dg/quad_3.f90 compilation failed to produce executable FAIL: gfortran.dg/read_eof_all.f90 execution test FAIL: gfortran.dg/short_circuiting.f90 (test for warnings, line 30) FAIL: gfortran.dg/storage_size_4.f90 (test for excess errors) UNRESOLVED: gfortran.dg/storage_size_4.f90 scan-tree-dump-not original "_gfortran_stop" FAIL: gfortran.dg/team_form_1.f90 (test for excess errors) UNRESOLVED: gfortran.dg/team_form_1.f90 compilation failed to produce executable FAIL: gfortran.dg/team_number_1.f90 (test for excess errors) UNRESOLVED: gfortran.dg/team_number_1.f90 compilation failed to produce executable === gfortran Summary === # of expected passes 23396 # of unexpected failures 20 # of expected failures 163 # of unresolved testcases 8 # of unsupported tests 56 I haven't looked at those failures yet. Maybe torture should be disabled another way, I'm not sure. Roman