This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch, testsuite, committed] Clean up gfortran.dg leftover module files.
- From: FX Coudert <fxcoudert at gmail dot com>
- To: Brooks Moses <brooks dot moses at codesourcery dot com>
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Mon, 26 Mar 2007 22:28:40 +0200
- Subject: Re: [patch, testsuite, committed] Clean up gfortran.dg leftover module files.
- References: <46082A94.2030709@codesourcery.com>
There are still a lot of module files left over from running
gfortran.fortran-torture, since (as Kaveh pointed out) that doesn't
recognize dg-final directives. I've got a patch that adds the
directives, but not one for recognizing them yet....
I'm wondering why we don't simply incorporate all these tests in the
gfortran.dg framework. It's rather easy to do, we just need to add
the compile tests a { dg-do compile } line, and the execution tests
both { dg-do run } and { dg-options "-w" }. There are a few special
cases (the execution tests associated to a .x file), but nothing too
difficult. We could even move them into subdirectory so we don't mix
everything.
Speaking of which: there's a gfortran.dg/g77 directory, but it looks
like the tests in it are never actually run when I do "make check-
gfortran". Is that expected?
FX