From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: OKURI-NASI
Date: Mon, 30 May 2022 17:22:29 +0200 [thread overview]
Message-ID: <87bkvfvydm.fsf@gnus.org> (raw)
In-Reply-To: <83k0a3jk8m.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 May 2022 15:08:41 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Why is that job single-threaded? leim has more than one file to
> build, so maybe we should rearrange the Makefile to allow a better
> parallelism? IOW, perhaps the single-threaded job you see is simply
> the result of all the other sub-jobs in leim being completed, and this
> is the only one that's left.
I think the other ones take so little time that it runs by itself for
most of the time.
> Or maybe remove ja-dic.el from the 'all:' target in leim/Makefile and
> move it to lisp/Makefile, where it will compete for CPU units with
> more jobs?
Yes, that's what I was thinking, but I wasn't sure how to express that
in Makefilese in the most idiomatic way, so if somebody else could do
that, that'd be nice.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-30 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 20:18 OKURI-NASI Lars Ingebrigtsen
2022-05-29 20:22 ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 2:28 ` OKURI-NASI Eli Zaretskii
2022-05-30 9:47 ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 11:39 ` OKURI-NASI Eli Zaretskii
2022-05-30 11:44 ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 11:49 ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 12:08 ` OKURI-NASI Eli Zaretskii
2022-05-30 15:22 ` Lars Ingebrigtsen [this message]
2022-06-01 2:54 ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 7:31 ` OKURI-NASI Stefan Kangas
2022-05-30 9:53 ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 13:06 ` OKURI-NASI Stefan Monnier
2022-05-30 13:19 ` OKURI-NASI Lars Ingebrigtsen
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkvfvydm.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).