This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: TESTCASE: STL's equal: Internal compiler error.
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: TESTCASE: STL's equal: Internal compiler error.
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Thu, 28 May 1998 23:15:49 -0600
- cc: Martin von Loewis <martin at mira dot isdn dot cs dot tu-berlin dot de>, egcs-bugs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <Pine.GSO.3.96.980528203545.18004k-100000@markab.dbai.tuwien.ac.at>you write:
> I wonder, however, whether there's also some existing documentation
> about the _structure_ of the testsuite tree? I.e., _where_ should one
> add _which_ kind of test cases?
For the C compiler there are two testing frameworks.
The "dg" tests and the "c-torture" tests.
c-torture is for generic tests -- ie, the test can/should operate
in the same manner regardless of the target configuration. Within
the c-torture framework is 3 significant test categories:
execution tests which must compile, link, execute and exit
with zero status if successful. else the test should call
abort.
compile tests which just have to compile
noncompile for tests which should produce compiler errors.
dg is for tests which don't fit into the c-torture framework and
allows much finer control over options, targets and other things.
The f-torture framework is much like the c-torture framework.
I barely know anything about the g++ old-deja framework (the g++.law
tests were actually written in the "mike-g++" framework and converted
by someone else to the old-deja framework a while back.
jeff