From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-71359-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 15922 invoked by alias); 2 Apr 2003 22:17:21 -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 15915 invoked from network); 2 Apr 2003 22:17:20 -0000
Received: from unknown (HELO mwinf0604.wanadoo.fr) (193.252.22.25)
  by sources.redhat.com with SMTP; 2 Apr 2003 22:17:20 -0000
Received: from ATuileries-101-1-3-130.abo.wanadoo.fr (ATuileries-101-1-3-130.abo.wanadoo.fr [193.251.48.130])
	by mwinf0604.wanadoo.fr (SMTP Server) with ESMTP
	id 722AF28002E9; Thu,  3 Apr 2003 00:17:19 +0200 (CEST)
Subject: Re: ACATS & GCC testsuite
From: Laurent Guerby <guerby@acm.org>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
In-Reply-To: <87k7ecfx2n.fsf@egil.codesourcery.com>
References: <10303281144.AA28312@vlsi1.ultra.nyu.edu>
	 <1048852101.10770.117.camel@localhost.localdomain>
	 <87k7ecfx2n.fsf@egil.codesourcery.com>
Content-Type: text/plain
Organization: 
Message-Id: <1049321838.1235.32.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Wed, 02 Apr 2003 23:00:00 -0000
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-04/txt/msg00102.txt.bz2

On Wed, 2003-04-02 at 22:45, Zack Weinberg wrote:
> When developing a patch I frequently sit in a cycle like this:
> 
> <edit edit edit>
> $ make cc1
> $ make check-gcc RUNTESTFLAGS="only/the/subset/I/care/about.exp"
> FAIL: ...
> 
> <repeat>
> 
> I would not mind much if final acceptance testing for patches was done
> on an installed tree, but I'll be unhappy if you break the above.

The first part of packaging ACATS is configuring the source,
know what to tweak and remove in the mass of tests
and track updates in the suite (quite low volume anyway).

Once it is done, running the test is just compiling
support sources (all the tests are using a few
common packages), then looping over the tests
doing gnatmake, run, check for "PASSED" in output.

I'll package the ACATS sources to be suitable
for integration in CVS and provide a simple
contrib script to run and report the status
with an installed compiler.

Any testing framework should be able to pick up the thing
easily from there. As I said in a previous email, I no longer 
intent to figure out configure, Makefile & DejaGNU in build trickery, 
so if someone has the knowledge to add such a thing, please feel free to do so. 
(Plus it will have to be redone if the GCC build structure change
and / or if the Ada runtime change.)

A simple Ada test showing support precompile and then
build'n run a test:

$ gcc -c support.adb
$ gnatmake test_ada
$ ./test_ada
PASSED test_ada


$ cat support.ads
package Support is
   procedure Report (S : in String; Passed : in Boolean);
end Support;
$ cat support.adb
with Ada.Text_IO;
package body Support is
   procedure Report (S : in String; Passed : in Boolean) is
   begin
      if Passed then
         Ada.Text_IO.Put_Line ("PASSED " & S);
      else
         Ada.Text_IO.Put_Line ("FAILED " & S);
      end if;
   end Report;
end Support;
$ cat test_ada.adb
with Support;
procedure Test_Ada is
begin
   Support.Report ("test_ada", True);
end Test_Ada;
$



-- 
Laurent Guerby <guerby@acm.org>