Re: how to add tests with input for g77?

[Jeffrey A Law <law at cygnus dot com>]

  In message <rzq67cbet0h.fsf@djlvig.dl.ac.uk>you write:
  > [I thought I'd saved some hints about this previously, but can't find
  > anything useful.  I've spent some time looking through dejagnu stuff
  > but again haven't found that profitable, sorry.]
  > 
  > How would I add g77 tests that require input when executing (probably
  > just on stdin) or, perhaps, take command-line args generally?
  > 
  > Also, how should any output files written to the execute directory be
  > cleaned up?  (That may be relevant for subsequent tests, depending on
  > how output files are opened.)
I don't think we've done any such tests within the torture frameworks in
the past.

It would be fine to extend the torture frameworks to handle this; my only
request would be that we somehow flag such tests as only available on native
platforms -- consider how you do IO on a board or pass arguments to simulated
programs.

We could have something like a .inp file for program inputs and some file
for expected output that the framework diffs against the actual output.

Similarly we could have a .argp file for test arguments.

jeff