unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Bootstrap optimization
Date: Thu, 25 Oct 2018 14:25:29 +0200	[thread overview]
Message-ID: <CAA2XvwJOgdnUOhH6Xnhy3qTOrybSeS7dfAoz7+tqBdu2e12prg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]

I find that the attached patch saves a few minutes for parallel builds on a
four core machine. What it does is to build both eval.go and psyntax.pp.go
serially before the rest is built in parallel (when make is given -j).

Here's an attempt at explanation why this saves time:

Let's denote the .go objects by numbers 1, 2, ... where 1 is eval.go and 2
is psyntax.pp.go. We also prepend a prefix "S" for a slow build with
interpreted psyntax.pp and "F" for a fast build.

Assuming a four core machine, we previously had something like:

S1
S2 S3 S4 S5
     S6 S7 S8 (since S2 builds so slowly)
F9 F10 ...

Now, instead, we have:

S1
S2
F3 F4 F5 F6
...

On my machine, the patch saved 10 minutes out of 55 minutes without the
patch.

To which branch should this be applied, stable-2.2 or master?

Best regards,
Mikael

[-- Attachment #1.2: Type: text/html, Size: 1191 bytes --]

[-- Attachment #2: 0001-Bootstrap-optimization.patch --]
[-- Type: text/x-patch, Size: 1122 bytes --]

From 0fe521100487411a2c48f6af14796a22964844a1 Mon Sep 17 00:00:00 2001
From: Mikael Djurfeldt <mikael@djurfeldt.com>
Date: Thu, 25 Oct 2018 13:53:47 +0200
Subject: [PATCH] Bootstrap optimization

* bootstrap/Makefile.am: Build both eval.go and psyntax-pp.go before the rest
  of the .go files so that they are handled by a fast macro expander. This
  saves time for a parallel build.
---
 bootstrap/Makefile.am | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/bootstrap/Makefile.am b/bootstrap/Makefile.am
index 57b62eb56..3e92ef1af 100644
--- a/bootstrap/Makefile.am
+++ b/bootstrap/Makefile.am
@@ -32,5 +32,8 @@ GUILE_OPTIMIZATIONS = -O1 -Oresolve-primitives
 include $(top_srcdir)/am/bootstrap.am
 
 # We must build the evaluator first, so that we can be sure to control
-# the stack.
-$(filter-out ice-9/eval.go, $(GOBJECTS)): ice-9/eval.go
+# the stack. Then, we build the syntax-case macro expander before the
+# rest, in order to speed up parallel builds.
+ice-9/psyntax-pp.go: ice-9/eval.go
+
+$(filter-out ice-9/eval.go ice-9/psyntax-pp.go, $(GOBJECTS)): ice-9/psyntax-pp.go
-- 
2.11.0


             reply	other threads:[~2018-10-25 12:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25 12:25 Mikael Djurfeldt [this message]
2018-10-28  1:34 ` Bootstrap optimization Mark H Weaver
2018-10-28  7:24   ` Mikael Djurfeldt
2018-10-28 12:40     ` Mikael Djurfeldt
2018-10-28 22:33       ` Officially require GNU Make to build Guile? (was Re: Bootstrap optimization) Mark H Weaver
2018-10-29  0:12         ` Greg Troxel
2018-10-29 10:33         ` Mikael Djurfeldt
2018-10-30  6:04           ` Mark H Weaver

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA2XvwJOgdnUOhH6Xnhy3qTOrybSeS7dfAoz7+tqBdu2e12prg@mail.gmail.com \
    --to=mikael@djurfeldt.com \
    --cc=guile-devel@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).