This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A testcase library
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>, <gcc at gcc dot gnu dot org>, <bangerth at ticam dot utexas dot edu>, <janis187 at us dot ibm dot com>, <ehrhardt at mathematik dot uni-ulm dot de>
- Date: Fri, 20 Dec 2002 20:02:16 +0000 (GMT)
- Subject: Re: A testcase library
On Fri, 20 Dec 2002, Jakub Jelinek wrote:
> Good work, thanks.
> Unless they are already in gcc testsuite, shouldn't they all be checked
> in after converting them to dg (or c-torture) format, ideally on all of 3.2/3.3
> branches and trunk?
Yes. The policy is in <http://gcc.gnu.org/bugs.html#manage>; it doesn't
specifically say what happens where the bug is already in GNATS and the
testcase is to be added, but it should be clear from the instructions that
you can add the testcase to the testsuite, include a comment in the
testcase referencing the PR and add a note referencing the testcase to the
PR, and mark the testcase XFAIL iff it's not a regression.
Release engineering has in the past involved people running the branch
testsuite against both branch and previous releases (instructions for
running with an installed GCC being provided) as an additional check for
regressions (which may show up those that are only regressions on some
platforms).
--
Joseph S. Myers
jsm28@cam.ac.uk