From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-42522-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 6763 invoked by alias); 10 Dec 2001 02:49:08 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 6741 invoked from network); 10 Dec 2001 02:49:06 -0000
Received: from unknown (HELO nile.gnat.com) (205.232.38.5)
  by sources.redhat.com with SMTP; 10 Dec 2001 02:49:06 -0000
Received: by nile.gnat.com (Postfix, from userid 338)
	id 0B259F28C7; Sun,  9 Dec 2001 21:48:20 -0500 (EST)
From: dewar@gnat.com
To: dewar@gnat.com, jsm28@cam.ac.uk
Subject: Re: ACATS legal status cleared by FSF
Cc: gcc@gcc.gnu.org
Message-Id: <20011210024820.0B259F28C7@nile.gnat.com>
Date: Sun, 09 Dec 2001 19:03:00 -0000
X-SW-Source: 2001-12/txt/msg00458.txt.bz2

<<Also, once we have a test harness for ordinary Ada tests similar to the
harnesses for other languages, contributing a test case for every change
ACT make unless there's some reason you can't (e.g. the harness doesn't
support it, or attempts to create a nonconfidential test case for a
problem shown up in confidential code fail), following the normal
requirements for contributing to GCC.  This way a useful test suite can
continue to be built up over time.
>>

Yes, naturally we will try to do this, but it is often not at all easy
to create stripped down test cases, and in such cases, it is better to have
the fix in the gcc tree with no test case, then to simply withhold the fix.