Re: [tree-ssa G95] make check-g95

[Steven Bosscher <s dot bosscher at student dot tudelft dot nl>]

Op wo 08-01-2003, om 00:48 schreef Joseph S. Myers:
> On 7 Jan 2003, Steven Bosscher wrote:
> 
> > Hi Diego, Paul,
> > 
> > This is the final piece we need for a G95 DejaGNU test framework.  From
> > now on, we can just drop our test cases in the (right) test suite
> > directories, et voila!
> 
> Thanks for drawing my attention to this additional place needing changing
> for new languages I missed when writing the checklist in sourcebuild.texi.  
> The system for language testsuites should be regularised: instead of rules
> in Makefile.in for each language, there should be rules in Make-lang.in,
> and the rule should be called <lang>.check as with other language
> Make-lang.in hooks.  The list of these hooks is in configure.in (which
> also has special logic for check_languages, which could be removed), and
> they are documented in sourcebuild.texi.  (Compatibility names, e.g.  
> check-c++ aliases, could stay in Make-lang.in alongside the regular names.
> The QMTest rules should properly also move to language subdirectories, but
> I don't know much about how they work.)
> 
> Changing things this way would make testsuites for new languages genuinely
> just drop in.

It would be even better if we would not have to change anything.

Did you notice that all the check-* targets execute exactly the same
code?

The only thing that is different is the name and the --tool parameter. 
The parameter is the language name, with the exception of "consistency"
So maybe we can just generate the check- targets for all configured
languages, and for a list of extra check-* targets.

The only problems
- deciding where that list would have to be defined.
- languages that have no test suite
- QMtest

The first is easy, and the second, I think, is a non-issue; Who writes a
a serious front end without a test suite.  The third, I know nothing
about.

Greetz
Steven