On 09/06/2011 01:56 PM, Arnaud Charlet wrote:
this means using as many processes as there are CPUs, right? It seems pretty
Right, but only for gnattools, which is a relatively short time, and
which always occurs at the end of the build (so with nothing else
running at the same time).
dubious
On 9/6/2011 7:14 AM, Duncan Sands wrote:
this means using as many processes as there are CPUs, right? It
seems pretty dubious to me to use more processes than the user maybe
asked for.
We often find that the optimum number of processes is a little bit more
than the number of physical processe
> this means using as many processes as there are CPUs, right? It seems pretty
Right, but only for gnattools, which is a relatively short time, and
which always occurs at the end of the build (so with nothing else
running at the same time).
> dubious to me to use more processes than the user may
Hi Arnaud,
Now that gnatmake supports -j0, it's possible to speed up the build of
gnattools during GNAT build by using gnatmake -j0 instead of gnatmake.
This is useful since gnattools is the only target which isn't parallelized
in the Makefile before this change.
this means using as many proc
Now that gnatmake supports -j0, it's possible to speed up the build of
gnattools during GNAT build by using gnatmake -j0 instead of gnatmake.
This is useful since gnattools is the only target which isn't parallelized
in the Makefile before this change.
Tested on x86_64-linux-gnu, committed on tru
