http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35015
Tobias Burnus changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35015
Bernhard Reutner-Fischer changed:
What|Removed |Added
Keywords||patch
URL|
--- Comment #7 from dfranke at gcc dot gnu dot org 2009-01-03 22:48 ---
(In reply to comment #4)
> Fair enough. We should thus apply the script to gcc/contrib/ (ok for
> adding it?) and consequently close this as fixed.
> thanks,
Hasn't been added yet. I think it's still useful.
Please
--- 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
--- Comment #5 from aldot at gcc dot gnu dot org 2008-01-29 20:35 ---
Several question marks for someone more familiar with the testsuite..
In the event that we can check against several multilib variants (?) that thus
match different dg-require (?), we may (?) eventually check against
--- Comment #4 from rep dot dot dot nop at gmail dot com 2008-01-29 20:23
---
Subject: Re: missing cleanup-modules directive in
testsuite/gfortran*
On Tue, Jan 29, 2008 at 08:15:23PM -, burnus at gcc dot gnu dot org wrote:
>--- Comment #3 from burnus at gcc dot gnu dot
--- Comment #3 from burnus at gcc dot gnu dot org 2008-01-29 20:15 ---
> You can pass any *.[fF][9]*[05]* and .inc into this script, it will happily
> scan for any un-cleaned mod. See top of the script for the files i initially
> fed to it.
Most (all?) .mod files which are left over com
--- Comment #2 from aldot at gcc dot gnu dot org 2008-01-29 16:05 ---
You can pass any *.[fF][9]*[05]* and .inc into this script, it will happily
scan for any un-cleaned mod. See top of the script for the files i initially
fed to it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35
--- Comment #1 from burnus at gcc dot gnu dot org 2008-01-29 15:36 ---
> This scripts emits on stdout a diagnostic message about
> a) wrong encoding in testcases (CRLF)
I think it is OK to mix \n and \r\n in the test suite as both should work. In
principle "\r" (old Mac files) should wo
