This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Doc correction regarding parallel builds
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: Daniel Egger <degger at fhm dot edu>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 20 Jun 2003 01:36:17 +0200 (CEST)
- Subject: Re: Doc correction regarding parallel builds
- References: <1054556220.24296.28.camel@sonja> <Pine.BSF.4.55.0306172112540.94125@naos.dbai.tuwien.ac.at><1055881930.14617.3.camel@sonja>
On Tue, 17 Jun 2003, Daniel Egger wrote:
> Patch attached. Here a suggestion for a changelog entry.
Thanks!
While reviewing the patch I made several changes and also rewrote the
first part of this paragraph. What do you think about the following?
Gerald
2003-06-20 Daniel Egger <degger@fhm.edu>
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* doc/install.texi (Building): Correct statement about parallel
builds.
Index: doc/install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.204
diff -u -3 -p -r1.204 install.texi
--- doc/install.texi 17 Jun 2003 21:28:05 -0000 1.204
+++ doc/install.texi 19 Jun 2003 23:34:01 -0000
@@ -1317,12 +1317,13 @@ Note that if an error occurs in any step
@section Building in parallel
-If you have a multiprocessor system you can use @samp{make bootstrap
-MAKE="make -j 2" -j 2} or just @samp{make -j 2 bootstrap}
-for GNU Make 3.79 and above instead of just @samp{make bootstrap}
-when building GCC@. You can use a bigger number instead of two if
-you like. In most cases, it won't help to use a number bigger than
-the number of processors in your machine.
+You can use @samp{make bootstrap MAKE="make -j 2" -j 2}, or just
+@samp{make -j 2 bootstrap} for GNU Make 3.79 and above, instead of
+@samp{make bootstrap} to build GCC in parallel.
+You can also specify a bigger number, and in most cases using a value
+greater than the number of processors in your machine will result in
+fewer and shorter I/O latency hits, thus improving overall throughput;
+this is especially true for slow drives and network filesystems.
@section Building the Ada compiler