It turned out that one warning output depended on details how
the testsuite it run. Thus, just ignore that bit that did not
always appear or not by using dg-prune-output.
Those subtle differences in test runs which make a test fail
or not fail, depending on how GCC's testsuite is run, make
life less boring ...
Committed as r12-3912-gce450af5087b95001b003184b8ecc2c9bbf65378.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht
München, HRB 106955
commit ce450af5087b95001b003184b8ecc2c9bbf65378
Author: Tobias Burnus <tob...@codesourcery.com>
Date: Tue Sep 28 09:49:12 2021 +0200
gfortran.dg/include_15.f90: Add dg-prune-output [PR102500]
gcc/testsuite/
PR fortran/102500
* gfortran.dg/include_15.f90: Add 'dg-prune-output' to prune
-Wmissing-include-dirs output printed or not depending on
how the testsuite is run.
diff --git a/gcc/testsuite/gfortran.dg/include_15.f90 b/gcc/testsuite/gfortran.dg/include_15.f90
index 068dcef5826..18d91f6cd32 100644
--- a/gcc/testsuite/gfortran.dg/include_15.f90
+++ b/gcc/testsuite/gfortran.dg/include_15.f90
@@ -4,3 +4,6 @@ end
! { dg-warning " /fdaf/: No such file or directory" "" { target *-*-* } 0 }
! { dg-warning " bar: No such file or directory" "" { target *-*-* } 0 }
! { dg-warning " foo/bar: No such file or directory" "" { target *-*-* } 0 }
+
+! Depending how the testsuite is run, it may or may not print the following warning:
+! { dg-prune-output "Warning: finclude: No such file or directory" }
