From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com, dj@redhat.com
Subject: (Toplevel patch) Let the top level run in parallel.
Date: Tue, 25 Feb 2003 21:22:00 -0000 [thread overview]
Message-ID: <20030225212219.GA28350@doctormoo> (raw)
It should be safe to run the top level in parallel thanks to the
serialization dependencies.
Tested on i686-pc-linux-gnu (on a single-processor machine, I'm afraid) via
'make -j 10 bootstrap' and 'make -j 10 all', just for the hell of it.
Both worked as expected. I really think this is safe.
* Makefile.tpl: Do run the top level in parallel.
* Makefile.in: Regenerate.
--- Makefile.tpl.old 2003-02-25 15:39:04.000000000 -0500
+++ Makefile.tpl 2003-02-25 16:15:16.000000000 -0500
@@ -728,7 +726,7 @@
.PHONY: check do-check
check:
- $(MAKE) do-check NOTPARALLEL=parallel-ok
+ $(MAKE) do-check
# Only include modules actually being configured and built.
do-check: @check_host_modules@ \
@@ -1259,7 +1257,7 @@
.PHONY: check-c++
check-c++:
- $(MAKE) check-target-libstdc++-v3 check-gcc-c++ NOTPARALLEL=parallel-ok
+ $(MAKE) check-target-libstdc++-v3 check-gcc-c++
.PHONY: install-gcc maybe-install-gcc
maybe-install-gcc:
@@ -1453,11 +1451,3 @@
.NOEXPORT:
MAKEOVERRIDES=
-
-# Tell GNU make 3.79 not to run the top level in parallel. This
-# prevents contention for $builddir/$target/config.cache, as well
-# as minimizing scatter in file system caches.
-NOTPARALLEL = .NOTPARALLEL
-$(NOTPARALLEL):
-
-# end of Makefile.in
next reply other threads:[~2003-02-25 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 21:22 Nathanael Nerode [this message]
2003-03-04 5:26 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030225212219.GA28350@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox