Re: GPC test suite (was: egcs-19980517 and gpc-980511)

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

  In message <199805272159.XAA00553@esmeralda.gerwinski.de>you write:
  > Hello,
  > 
  > I think that the `gpc-test.tar.gz' test suite should become "the"
  > test suite for GPC.  It is much more complete than the existing
  > DejaGNU test suite.
What I'm talking about is converting that testsuite to the dejagnu
format.  The other possibility is to write a dejagnu driver to
run that testsuite.  However, that's generally more work than
sorting out the existing tests into a "torture" framework.

  > >   * Tests which should compile & execute.  These tests should
  > >   call abort when they fail or exit (0) when they pass.
  > 
  > For the current test suite it is important that the test programs
  > produce the correct output.
We could probably enhance the testsuite to check for specific
output of a test -- we already do that for stuff like libio/libstdc++.

Or you tweak the tests to put their output into a string, then have
the test check the contents of the string for correctness and do the
right thing re: exit/abort.  Several of the C torture tests do this
kind of thing.

  > Let's hope that it is able to give some special flags to the compiler
  > which are needed for that specific test (marked with "FLAG" in the
  > test source).
What kind of flags do you need to give to trigger the test?  THe
torture framework is design to run through a set of common flags
(usually optimization options) for all tests.

There are ways to pass specific flags to specific tests, but it's
frowned upon in the torture framework.


jeff