This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ada/5909] Ada has no test suite.
- From: "jsm at polyomino dot org dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Oct 2003 14:05:55 -0000
- Subject: [Bug ada/5909] Ada has no test suite.
- References: <20020310103601.5909.zack@codesourcery.com>
- Reply-to: 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 jsm at polyomino dot org dot uk 2003-10-22 14:05 -------
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.
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 ...?
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)?
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.