From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-101654-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 23769 invoked by alias); 30 Aug 2004 22:52:44 -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 23761 invoked from network); 30 Aug 2004 22:52:44 -0000
Received: from unknown (HELO nile.gnat.com) (205.232.38.5)
  by sourceware.org with SMTP; 30 Aug 2004 22:52:44 -0000
Received: from localhost (localhost [127.0.0.1])
	by nile.gnat.com (Postfix) with ESMTP
	id B4070F2E00; Mon, 30 Aug 2004 18:52:43 -0400 (EDT)
Received: from nile.gnat.com ([127.0.0.1])
 by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP
 id 03026-01-8; Mon, 30 Aug 2004 18:52:43 -0400 (EDT)
Received: from [127.0.0.1] (ppp3.gnat.com [205.232.38.213])
	by nile.gnat.com (Postfix) with ESMTP
	id A534FF2DF5; Mon, 30 Aug 2004 18:52:40 -0400 (EDT)
Message-ID: <4133AFBF.1030707@gnat.com>
Date: Mon, 30 Aug 2004 23:00:00 -0000
From: Robert Dewar <dewar@gnat.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
MIME-Version: 1.0
To: Mike Stump <mrs@apple.com>
Cc: "Joseph S. Myers" <jsm@polyomino.org.uk>, gcc@gcc.gnu.org,
	Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Subject: Re: Ada policy
References: <10408302121.AA00131@vlsi1.ultra.nyu.edu> <4133A965.8040200@gnat.com> <Pine.LNX.4.61.0408302230070.15526@digraph.polyomino.org.uk> <05070D42-FAD6-11D8-8516-000393941EE6@apple.com>
In-Reply-To: <05070D42-FAD6-11D8-8516-000393941EE6@apple.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at nile.gnat.com
X-SW-Source: 2004-08/txt/msg01544.txt.bz2

Mike Stump wrote:
> On Aug 30, 2004, at 3:34 PM, Joseph S. Myers wrote:
> 
>> Bugs shown by proprietary testcases should indeed be fixed.  But each
>> individual patch submission that can't include a testcase should 
>> include a
>> statement of why (e.g. that the test is proprietary and a synthetic one
>> not readily producable
> 
> 
> I think that one can misuse `readily producible'.  Certainly when I 
> spend hours upon hours trimming a testcase, I'm not feeling like the 
> testcase is readily producible, but I do it anyway.

It's certainly great that you have the bandwidth do do this, no one
would think otherwise.