make -j2 check-gfortran

Tobias Burnus tobias.burnus@physik.fu-berlin.de
Tue Oct 20 15:04:00 GMT 2009


Hi Janus,

> just a quick question: What's the status of running the testsuite via
> a parallel make? Is this supposed to work?

Yes - it should work and I use it regularly. It is implemented by having
several make targets, which have been manually defined by Jakub. For
each make target you get a summary printed. Thus you don't look at only
one summary (as for "make check-gfortran") but at several.

While it can be a bit confusing and one needs to be careful to miss not
a FAIL in all the output, it is still nice because of the speedup.

I think the reason for getting four summaries is that gfortran has been
split into four make targets, which are called either in parallel (-j 4
or heigher) or semi-parallel ( -j 2 or -j3, running 2 or 3 in parallel
and then the remaining one).

Life would be easier if DejaGnu would itself run in parallel.

If you have yet another window, you can also run "cd */libgomp; make check"
which also contains some Fortran tests (which I managed to break once).

Tobias

PS: Regarding the use of "-j <n>" on the test suite: (almost) all
middle-end developers use it all the time. They need to run
"make -k check" (all (!) languages) - which takes significantly
longer than just "make check-gfortran".



More information about the Fortran mailing list