------- Comment #6 from fxcoudert at gcc dot gnu dot org 2008-02-03 14:34
-------
(In reply to comment #5)
> In the event that we can check against several multilib variants (?) that thus
> match different dg-require (?), we may (?) eventually check against stale
> module data if a "board" does not cleanup-modules after itself and each board
> is run in the same directory (where an old multilib-run may have left old
> output/modules), no?
I don't think so, since each a newer version of the module file is written
every time before being read. It still would be nice to have to way to support
a cleanup directive in the gfortran.fortran-torture/ directory.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2008-02-03 14:34:44
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35015
