http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50288
--- Comment #10 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-09-05
15:19:17 UTC ---
(In reply to comment #9)
> I think one should also do this for class_4{a-d}.f03, where Tobias apparently
> worked around the problem by adding an extra file (just to do the cleanup).
Thanks for the honor but that was Paul's patch (cf. PR 40440). The big
difference is: That's a "dg-do compile" patch. (I might have added a mod
cleanup to one of the files.)
And no, it does not make sense there. The issue only occurs for "dg-do run" -
as after each compile/run, the cleanup is done. But with dg-do compile as with
dg-do run-once, one has only a single run. Thus, that the .mod file from the
previous test is removed, does not matter.
> Also, I still don't understand why I did not see the problem. Maybe this could
> be due to different dejagnu versions (mine is 1.4.4)?
No idea, but I have also 1.4.4 installed - and I do see - as expected - the
failure.
