This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
gcc parallel make check
- From: "VandeVondele Joost" <joost dot vandevondele at mat dot ethz dot ch>
- To: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 3 Sep 2014 09:15:51 +0000
- Subject: gcc parallel make check
- Authentication-results: sourceware.org; auth=none
- References: <908103EDB4893A42920B21D3568BFD93150E8FDF at MBX13 dot d dot ethz dot ch>
I've noticed that
make -j -k check-fortran
results in a serialized checking, while
make -j32 -k check-fortran
goes parallel. Somehow the explicit 'N' in -jN seems to be needed for the check target, while the other targets seem to do just fine. Is that a feature, or should I file a PR for that... ?
Somewhat related.... is there a rule of thumb on how is the granularity of parallel check decided ? E.g. check-fortran seems to be limited to about ~5 parallel targets, which is few for a typical server (but of course a welcome speedup already).
Thanks,
Joost