[Bug testsuite/102394] New: Gfortran testsuite could avoid target specific tests

[Bug testsuite/102394] New: Gfortran testsuite could avoid target specific tests

[rimvydas.jas at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102394

            Bug ID: 102394
           Summary: Gfortran testsuite could avoid target specific tests
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rimvydas.jas at gmail dot com
  Target Milestone: ---

Given latest gcc/testsuite/gfortran.dg/c-interop/ failures it might be a good
time generalize most of gcc/testsuite/gfortran.dg/ tests for easier detection
of skipped tests. This could avoid a need to add gcc/testsuite/gfortran.target/
in the future.  Currently there are over 80 UNSUPPORTED tests on
x86_64-unknown-linux-gnu.  Most of them are trivial to make generic, including
winapi.f90.

[Bug testsuite/102394] Gfortran testsuite could avoid target specific tests

[rimvydas.jas at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102394

--- Comment #1 from Rimvydas (RJ) <rimvydas.jas at gmail dot com> ---
Created attachment 51475
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51475&action=edit
possible generalizations

                === gfortran Summary ===

-# of expected passes           60534
+# of expected passes           60602
 # of expected failures         507
 # of unresolved testcases      30
-# of unsupported tests         82
+# of unsupported tests         1
 /build/trunk/gcc/gfortran  version 12.0.0 20210918 (experimental) [master
r12-3643-g18b57c1d4a8] (GCC)

UNSUPPORTED: gfortran.dg/prof/dynamic_dispatch_6.f03 -fauto-profile
that requires perf(1) and autofdo.

[Bug testsuite/102394] Gfortran testsuite could avoid target specific tests

[rimvydas.jas at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102394

--- Comment #2 from Rimvydas (RJ) <rimvydas.jas at gmail dot com> ---
Also with updated toolchain to glibc-2.34 (still not sure if this was not
happening before) noticed that very rarely one test in particular sometimes
fail during parallel check-gcc-fortran. Running explicitly is more
reproducible, STOP 1, irnk == -1000:
make -j20  check-gcc-fortran RUNTESTFLAGS=dg.exp=PR93963.f90

FAIL: gfortran.dg/PR93963.f90   -O1  execution test
                === gfortran Summary ===
# of expected passes            11
# of unexpected failures        1