[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Justification for separate ${tool}-dg.exp
From: |
Rainer Orth |
Subject: |
Justification for separate ${tool}-dg.exp |
Date: |
Fri, 04 Feb 2011 10:51:51 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.2 (usg-unix-v) |
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.
Comments?
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Justification for separate ${tool}-dg.exp,
Rainer Orth <=