This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: QMTest and the G++ testsuite



> That's definitely an interesting feature, and one that I've wanted in
> DejaGNU for a while, until I realized that parallel testing didn't
> improve time at all on my uni-processor Athlon box.  But in the cases
> where it would actually make a difference in multi-processor machines,
> e.g. when testing a toolchain with dozens of multilibs, I can already
> test in parallel with a Makefile hack introduced a while ago.

Concretely, using QMTest to test g++ on a two-processor x86 box testing
the i686-pc-linux-gnu toolchain (no multilibs), I can run
"make qmtest-g++" in less than half the time than with "make check-g++".

Sure, if you're building a full toolchain, you can use "make -j".  But
that's not the only scenario.

I'm asking for a baby step: that we permit people to use QMTest to do
their testing, rather than requiring DejaGNU.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]