On 08/13/2013 04:06 AM, Thomas Schwinge wrote: > Hi! > > I noticed something strange in the libgomp testresults (but not > necessarily specific to libgomp): an "arbitrary" set of the Fortran > execution tests are run just for -O, and others for each of the full set > of torture options: -O0, -O1, -O2, and so on. After some time I realized > it's the set of tests that contain an explicit »dg-do run« directive that > are run for all torture levels, and the tests that inherit the default > »set dg-do-what-default run« from libgomp/testsuite/lib/libgomp.exp are > only run for -O. This is coming from the special handling in > gcc/testsuite/lib/gfortran-dg.exp:gfortran-dg-test (which seems to be > present approximately "forever"). Should this consider the > dg-do-what-default case, too? Why is torture testing done only for > execution tests? And, why only for Fortran? Is this behavior generally > intentional -- of course, bigger testing coverage is nice, but this seems > a bit arbitrary to me?
You're right, it looks odd, but I can't say whether it's right or wrong. Sometimes these things just grow over the years. Fortran people might want to take a closer look to see how they want the tests to be run now. gfortran.fortran-torture/compile has torture tests for Fortran compiles, and C has torture tests for both compile and execute in a couple of places. Janis
