[Bug ada/5909] Ada has no test suite.

["laurent at guerby dot net" <gcc-bugzilla at gcc dot gnu dot org>]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5909



------- Additional Comments From laurent at guerby dot net  2003-10-22 17:40 -------
Subject: Re:  Ada has no test suite.


> On Wed, 22 Oct 2003, charlet at gcc dot gnu dot org wrote:
> 
> > I have a complete set up which is working. Since Laurent and I know nothing
> > about dejagnu, we're simply using sh to run the test suite, which is
> > working just fine.

If someone is willing to contribute a dejagnu Ada harness, we're
ready to use it, otherwise we'll do with simple scripts.

> But is it working for testing cross-compilers where programs for the
> target need to be run on a simulator, or on an embedded board, or ...? 

Joel Sherrill did run my original script with a cross-compiler
on a simulator and IIRC he had trouble running dejagnu (much
more complicated to set up).

>  
> And does it generate .sum files in the Dejagnu format for the use of the
> automated regression testers (this point is critical to get much of the
> benefit of the testing, a sh script can always be committed first then
> converted to a Dejagnu harness later to take advantage of all the support
> Dejagnu has for testing cross-compilers)?

If the format and where to put the ".sum" files is documented, that
should be easy to add.

> Does your test setup support additionally "ordinary" testsuite directories
> for gradually accumulating tests in the style of
> gcc.c-torture/{compile,execute} (test compilation / execution works with
> multiple optimization options) or gcc.dg (test that error/warning messages
> are as expected)?  There are many such tests that Kenner has posted to the 
> lists over the years (for back-end bugs shown up by Ada testcases) that 
> should be gathered into the testsuite.

At -O0 the current ACATS run is done in 45 minutes on a P3 1GHz. We can
easily add a loop over compile options, but at some point
there will be some thinking about what we want to require for patch
and what is optional in the GCC testsuites.

ACT also has a small set of tests which are not proprietary code
and could be included, adding a loop over them in the
ACATS script is easy. I'll go back in the list archives
and add them over the time.

Laurent