From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 863 invoked by alias); 8 Dec 2001 02:38:49 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 614 invoked from network); 8 Dec 2001 02:37:28 -0000 Received: from unknown (HELO mail.wrs.com) (147.11.1.11) by sources.redhat.com with SMTP; 8 Dec 2001 02:37:28 -0000 Received: from kankakee.wrs.com (kankakee [147.11.37.13]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id SAA29071; Fri, 7 Dec 2001 18:35:23 -0800 (PST) From: mike stump Received: (from mrs@localhost) by kankakee.wrs.com (8.9.3+Sun/8.9.0) id SAA14563; Fri, 7 Dec 2001 18:36:12 -0800 (PST) Date: Fri, 07 Dec 2001 18:50:00 -0000 Message-Id: <200112080236.SAA14563@kankakee.wrs.com> To: dewar@gnat.com, kenner@vlsi1.ultra.nyu.edu, zack@codesourcery.com Subject: Re: ACATS legal status cleared by FSF Cc: gcc@gcc.gnu.org X-SW-Source: 2001-12/txt/msg00409.txt.bz2 > From: dewar@gnat.com > To: kenner@vlsi1.ultra.nyu.edu, zack@codesourcery.com > Cc: gcc@gcc.gnu.org > Date: Fri, 7 Dec 2001 20:39:54 -0500 (EST) > < the test harness does is to check for the presence of at least one > error line for each line marked ERROR. I don't know how hard such a > harness is to write, and that's not the way B tests are usually done, but > might work. > >> > That's not good enough, the errors often do not occur on exactly the correct > lines. We have years of experience with such a scheme for C++, it works, it is useful, it isn't a maintenance burden. I find the value of it easily outweighs the maintenance cost of it. If your compiler randomly changes around where messages come out all the time, maybe you should re-engineer it from the top down, fix all of them to be correct, once, fix the testcases in the testsuite to conform to it, and then refuse any changes to this status quo for 5-10 years, and then after 5 years, put in all the changes enmass you would like, redo the testsuite, lather, rise, repeat.