This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [ada, testsuite] gnat.dg cleanup
Arnaud Charlet <charlet@adacore.com> writes:
>> This is not for every test, but only for those that use other packages.
>> For all others, it's already automatic. Like you, I'd consider anything
>> else inappropriate.
>
> The problem is that the current infrastructure already is very unfriendly
> to multiple file tests, so this change is making it a bit more unfriendly,
> so that's not really going in the right direction unfortunately (and is
> probably one of the reasons there are not more t ests in this category).
That's true, unfortunately. I'm experiencing the same when converting
boehm-gc to DejaGnu which has one test that needs a shared library to be
built separately. Getting this (and the subsequent cleanup) done proved
unexpectedly hard.
>> I don't know if it's easy to deduce the list of used packages inside the
>> testsuite framework. At the moment, this annotation is only necessary
>> for 58 out of 840 files in gnat.dg, which I wouldn't consider too heavy
>> a burden on the maintainers. In fact, it took me quite some time to get
>> the lists right, especially in gnat.dg/specs.
>>
>> If you have suggestions on how to automate this, I'd be happy to listen.
>
> What about running each test under a separate temp dir (perhaps that's
> already what's done?) and systematically suppressing *.o *.ali *.s *.gimple?
It's not: separate dirs are only used when when running the same tool
(gnat in this case) in parallel on separate distinct parts of the
testsuite. I don't yet know how hard it would be to coerce DejaGnu to
do this. As an alternative, is it possible to detect the list of
additional packages used by the package under test? If so, this
information could easily be used for automatic cleanup.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University