This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: how to add tests with input for g77?
- To: Dave Love <d dot love at dl dot ac dot uk>
- Subject: Re: how to add tests with input for g77?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 02 Dec 1998 18:37:20 -0700
- cc: egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <rzqhfvubexq.fsf@djlvig.dl.ac.uk>you write:
> >>>>> "Jeff" == Jeffrey A Law <law@cygnus.com> writes:
>
> Jeff> It would be fine to extend the torture frameworks to handle
> Jeff> this;
>
> I'm not going to be able to, I'm afraid. Would anyone with a
> deja-clue care to volunteer? This would certainly be useful for g77
> tests.
"deja-clue" I like it :-)
I think the way to go is to look at some of the libstdc++/libio dejagnu
tests. They know how to read from files and compare generated output to
an expected output file.
> 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?
Which ones write files? I haven't actually tried to run the fortran tests
for an embedded target yet. But typically an embedded board doesn't have
a convienent way to do file I/O or to pass arguments to programs. They may
not even have terminal I/O. But they usually have stubs which allow linking
even though the target doesn't have I/O capabilities.
Simulators typically have enough brains to do I/O to a unix filesystem using
unix system call emulation.
I'd like us to start thinking about solving these problems (we don't have to
actually solve them now, just be aware of the problem and get some grey matter
thinking about solutions).
jeff