Re: how to add tests with input for g77?

[Dave Love <d dot love at dl dot ac dot uk>]

>>>>> "Jeff" == Jeffrey A Law <law@hurl.cygnus.com> writes:

 Jeff> I think the way to go is to look at some of the libstdc++/libio
 Jeff> dejagnu tests.  They know how to read from files and compare
 Jeff> generated output to an expected output file.

I'll look, but I'm not on for Tcl hacking, I'm afraid.

 >> We already have some fortran tests that write files, if that's the
 >> issue (the runtime could always produce error messages).  Can someone
 >> let me know how they need to be fixed?
 Jeff> Which ones write files?

io[01].f and u77-test.f, at least.

 Jeff> I haven't actually tried to run the fortran tests
 Jeff> for an embedded target yet.

It doesn't seem worth effort in the absence of anyone being interested
(no complaints!).

 Jeff> But typically an embedded board doesn't have a convienent way
 Jeff> to do file I/O or to pass arguments to programs.  They may not
 Jeff> even have terminal I/O.

Avoiding stdio for Fortran tests probably isn't practical and
certainly isn't something I want to spend time on unless there's
actually a use for g77 on such systems.

[I am trying to get a conformance suite operating, which won't be
complete without i/o.]