From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: please make byte compiling during bootstrap take advantage of make -j
Date: Sun, 04 May 2008 21:49:22 +0300 [thread overview]
Message-ID: <u7ie9x5u5.fsf@gnu.org> (raw)
In-Reply-To: <200805041735.m44HZbxS018196@sallyv1.ics.uci.edu>
> From: Dan Nicolaescu <dann@ics.uci.edu>
> Date: Sun, 04 May 2008 10:35:36 -0700
>
>
> Multi-core CPUs are already widespread, and will only become more so.
>
> Byte compiling all the elisp files is where most of the time is spent
> during bootstrap. But currently byte compilation does not take
> advantage of "make -j", which would speed it up a great deal.
>
> Can you please implement this?
There's this comment in lisp/Makefile.in:
# Files MUST be compiled one by
# one. If we compile several files in a row we can't make sure that
# the compilation environment is clean.
I have only a vague idea of what is this trying to say, but assuming
that this consideration is not important for several compilations
going on in parallel, doing what you want boils down to making the
`compile:' target depend on all the .elc files; the rest will be done
automatically by Make.
next prev parent reply other threads:[~2008-05-04 18:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18495.14322.3139.653674@fencepost.gnu.org>
2008-05-04 17:35 ` please make byte compiling during bootstrap take advantage of make -j Dan Nicolaescu
2008-05-04 18:49 ` Eli Zaretskii [this message]
2008-05-05 18:15 ` Glenn Morris
2008-05-07 3:05 ` Glenn Morris
2008-05-07 9:47 ` Eli Zaretskii
2008-05-07 22:33 ` Glenn Morris
2008-05-08 10:30 ` Eli Zaretskii
2008-05-08 19:34 ` Glenn Morris
2008-05-09 6:32 ` Eli Zaretskii
2008-05-09 7:02 ` Dan Nicolaescu
2008-05-09 7:41 ` Eli Zaretskii
2008-05-07 17:34 ` Richard M Stallman
2008-05-29 23:20 ` bug#189: marked as done (please make byte compiling during bootstrap take advantage of make -j) Emacs bug Tracking System
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=u7ie9x5u5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=dann@ics.uci.edu \
/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).