From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 34982@debbugs.gnu.org
Subject: [bug#34982] [PATCH] guile-build-system: Support building in parallel.
Date: Sat, 30 Mar 2019 11:56:33 +0100 [thread overview]
Message-ID: <87lg0w4om6.fsf@gnu.org> (raw)
In-Reply-To: <20190324212345.4697-1-mail@cbaines.net> (Christopher Baines's message of "Sun, 24 Mar 2019 21:23:45 +0000")
Hi,
Christopher Baines <mail@cbaines.net> skribis:
> * guix/build/guile-build-system.scm (build): Use n-par-for-each, instead of
> for-each, to use multiple cores if available.
[...]
> + (n-par-for-each
> + (parallel-job-count)
> + (lambda (file)
> + (catch #t
> + (lambda ()
> + (let* ((go (string-append go-dir
> + (file-sans-extension file)
> + ".go")))
> + ;; Install source module.
> + (install-file (string-append source-directory "/" file)
> + (string-append module-dir
> + "/" (dirname file)))
>
> - ;; Install and compile module.
> - (apply invoke guild "compile" "-L" source-directory
It probably doesn’t matter that much, but it feels wrong to create
threads that do nothing but call ‘waitpid’, essentially.
Commit f07041f7d25badb7d74b8fad6ee446a12af04f63 removed a ‘p-for-each’
procedure that could be useful here since it directly creates N
processes and then does (waitpid WAITPID_ANY). Would it make sense to
paste it here and use it in lieu of ‘n-par-for-each’?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-03-30 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 21:23 [bug#34982] [PATCH] guile-build-system: Support building in parallel Christopher Baines
2019-03-30 10:56 ` Ludovic Courtès [this message]
2019-04-05 23:33 ` Christopher Baines
2019-04-05 23:50 ` [bug#34982] " Christopher Baines
2019-04-16 17:06 ` Ludovic Courtès
2019-04-16 18:25 ` Christopher Baines
2019-04-16 18:13 ` Christopher Baines
2019-04-16 19:30 ` Ludovic Courtès
2019-04-19 7:43 ` bug#34982: " Christopher Baines
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=87lg0w4om6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34982@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.