[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Justification for separate ${tool}-dg.exp
From: |
Ben Elliston |
Subject: |
Re: Justification for separate ${tool}-dg.exp |
Date: |
Wed, 2 Mar 2011 21:45:48 +1100 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
Hi Rainer
On Fri, Feb 04, 2011 at 10:51:51AM +0100, Rainer Orth wrote:
> While reviewing the GCC testsuite, I noticed that practically every
> testsuite driver has the equivalent of
>
> load_lib ${tool}-dg.exp
>
> While ${tool}.exp is automatically loaded by the framework, this file
> needs to be loaded separately.
>
> It is sort of documented in dg.exp:
>
> # The normal way to write a testsuite is to have a .exp file containing:
> #
> # load_lib ${tool}-dg.exp
> # dg-init
> # dg-runtest [lsort [glob -nocomplain $srcdir/$subdir/foo*]] ...
> # dg-finish
>
> but so far I've no idea what the point is and how to decide what goes
> into ${tool}.exp and what into ${tool}-dg.exp. Unless there is a good
> reason for this separation, I plan to go over the GCC testsuites and
> remove the explicit load_lib and do that in the corresponding
> ${tool}.exp until both are merged.
I don't know. I think the best person to ask this question is Doug
Evan. Doug, can you remember? :-)
Ben
- Re: Justification for separate ${tool}-dg.exp,
Ben Elliston <=