This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/20567] dg-options in gcc.c-torture
- From: "aldot at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 22 Mar 2012 13:36:09 +0000
- Subject: [Bug testsuite/20567] dg-options in gcc.c-torture
- Auto-submitted: auto-generated
- References: <bug-20567-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20567
Bernhard Reutner-Fischer <aldot at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aldot at gcc dot gnu.org
--- Comment #6 from Bernhard Reutner-Fischer <aldot at gcc dot gnu.org> 2012-03-22 13:36:09 UTC ---
(In reply to comment #4)
> The gfortran torture tests also need to support dg- options, starting with
> dg-final to allow cleaning up module files from the testsuite temporary
> directory.
implicit cleanup-modules in all gfortran related tests were recently
implemented, see testsuite/lib/fortran-modules.exp
I did not look if all torture tests pull in dg- nowadays (gcc.c-torture/compile
and gcc.c-torture/execute/ieee seem to include dg as opposed to the rest, from
a short look. Little bit of a mess, imho).
Is there consensus that all testcases should use dg (or gcc-dg) ?