Re: PATCH: Run V3 tests on installed compiler

[Mark Mitchell <mark at codesourcery dot com>]

Benjamin Kosnik wrote:

> I dunno dude. This is pretty much a deal breaker for me: I've got to be
> able to do something like this, preferably by editing testsuite_files directly.

Sure; you definitely have to have a way to name tests to run.

I'm pretty mystified.

Is anyone else able to confirm or deny that the bit with normal.exp and 
testsuite_files works for them?

Benjamin, if you're in $objdir/gcc, does:

  runtest --tool g++ dg.exp='ptrmem*.C'

work for you?  (That's a similar incantation for running just a few 
tests from the G++ testsuite.)  There's not really anything special 
about the receipe I gave; that's completely stock DejaGNU.

In fact, this works for me too:

  runtest --tool libstdc++ normal.exp='17_intro/*.cc'

                === libstdc++ Summary ===

# of expected passes            46

What if you have just a few files in testsuite_files?  Is this something 
where your shell is truncating the list?

Does plain "make check" in V3 give you the expected results?

Worst case, we do as you suggested, and read testcase_files if it exists.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304