From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Volker Reichelt <reichelt@igpm.rwth-aachen.de>,
<gcc@gcc.gnu.org>, <bangerth@ticam.utexas.edu>,
<janis187@us.ibm.com>, <ehrhardt@mathematik.uni-ulm.de>
Subject: Re: A testcase library
Date: Fri, 20 Dec 2002 15:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0212201958060.29051-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20021220125202.B1310@sunsite.ms.mff.cuni.cz>
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
next prev parent reply other threads:[~2002-12-20 20:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 8:12 Volker Reichelt
2002-12-20 8:14 ` Jakub Jelinek
2002-12-20 8:50 ` Volker Reichelt
2002-12-20 9:12 ` Eric Botcazou
2002-12-20 9:32 ` Wolfgang Bangerth
2002-12-20 10:51 ` Volker Reichelt
2002-12-20 12:02 ` Jason R Thorpe
2002-12-22 22:44 ` Ben Elliston
2002-12-23 12:46 ` Mike Stump
2002-12-23 12:57 ` Daniel Jacobowitz
2002-12-23 15:54 ` Mike Stump
2002-12-23 16:35 ` Daniel Jacobowitz
2002-12-23 13:50 ` Ben Elliston
2002-12-23 14:00 ` Zack Weinberg
2002-12-23 15:27 ` Daniel Jacobowitz
2002-12-20 15:01 ` Joseph S. Myers [this message]
2002-12-23 18:08 Richard Kenner
2002-12-24 12:30 ` David Carlton
2002-12-23 18:42 Richard Kenner
2002-12-23 21:57 ` Daniel Jacobowitz
2002-12-24 12:28 ` David Carlton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.33.0212201958060.29051-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=bangerth@ticam.utexas.edu \
--cc=ehrhardt@mathematik.uni-ulm.de \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=janis187@us.ibm.com \
--cc=reichelt@igpm.rwth-aachen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).