gcc/testsuite at bfd7f4ecc75404c80b575bb9bd35cad4e78e5a1f - gcc

History

Gabriel Dos Reis db353c2c69 .cc: Remove explicit reference to 'testsuite/' in testcases. testsuite/27_io/.cc: Remove explicit reference to 'testsuite/' in testcases. Prepare for the DejaGnu based framework. mkcheck.in: Adjust call to tests_flags. Don't mmkdir testsuite directory -- it is now mkcheck working directory. * tests_flags.in: Remove reference to $(top_srcdir). Use ${SRC_DIR} instead. * Makefile.am (check, check-install): Change mkcheck invocation logic. * Makefile.in: Regenerate. From-SVN: r39255		2001-01-25 04:09:22 +00:00
..
17_intro	17_intro: Prepare testcases for new style DejaGnu framework.	2001-01-19 02:52:27 +00:00
18_support
20_util
21_strings	C++STYLE (classname): Add more existing and stylish patterns.	2001-01-16 07:55:26 +00:00
22_locale
23_containers	acinclude.m4, [...]: Change sourceware.cygnus.com and sources.redhat.com URLs for libstdc++ web...	2000-12-21 22:08:39 +00:00
24_iterators
25_algorithms	acinclude.m4, [...]: Change sourceware.cygnus.com and sources.redhat.com URLs for libstdc++ web...	2000-12-21 22:08:39 +00:00
26_numerics
27_io	*.cc: Remove explicit reference to 'testsuite/' in testcases.	2001-01-25 04:09:22 +00:00
ext
lib	libstdc++.exp: Improve.	2001-01-23 02:48:27 +00:00
libstdc++.tests	tests.exp: New file.	2001-01-20 05:09:08 +00:00
debug_assert.h
printnow.c
README	libstdc++.exp: Improve.	2001-01-23 02:48:27 +00:00

README

We're in the process of converting the existing testsuite machinery to
use the new style DejaGnu framework.  Eventually, we'll abandon
../mkcheck.in in favor of this new testsuite framework.  

  Basically, a testcase contains dg-keywords (see dg.exp) indicating
what to do and what kind of behaviour are to be expected.  New
testsuite should be written with the new style DejaGnu framework in mind.

  The V3 testing framework supports additional keywords for the purpose
of easing the job of writing testcases.  All V3-keywords are of the
form @xxx@.  Currently supported keywords include:

  @require@ <files>
      The existence of <files> is essential for the test to complete
      successfully.  For example, a testcase foo.C using bar.baz as
      input file could say
	    // @require@ bar.baz
      The special variable % stands for the rootname, e.g. the
      file-name without its `.C' extension.  Example of use (taken
      verbatim from 27_io/filebuf.cc)
	   // @require@ %-*.tst %-*.txt

  @diff@ <first-list> <second-list>

-- Gaby