From: Paul Eggert <eggert@cs.ucla.edu>
To: bruce.connor.am@gmail.com, Glenn Morris <rgm@gnu.org>
Cc: 20887@debbugs.gnu.org
Subject: bug#20887: 'make bootstrap' now verrrry slow due to recent isearch changes
Date: Wed, 24 Jun 2015 06:36:16 -0700 [thread overview]
Message-ID: <558AB250.5040908@cs.ucla.edu> (raw)
In-Reply-To: <CAAdUY-JccFPdWeodbZj1rXHJgEkwtsa7CViZeA97Qniw8Lg2uA@mail.gmail.com>
Artur Malabarba wrote:
> Does anyone know what could cause these 4 seconds to become 5 min
> during bootstrap?
I'm not sure, but during bootstrap, the compiler hasn't been compiled yet; it's
being interpreted. So it's very slow. The build process attempts to compile
the compiler first, so that the rest of the build finishes faster, but the early
part of the bootstrap must be done with a slow compiler.
> Does bootstrap compile the file 60 times? =P
Yes, it seems so. With a slow compiler. It takes hours. It's really bad.
Please try the recipe I gave Glenn:
rm -f src/bootstrap-emacs src/emacs $(find . -name '*.elc')
make
next prev parent reply other threads:[~2015-06-24 13:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 1:35 bug#20887: 'make bootstrap' now verrrry slow due to recent isearch changes Paul Eggert
2015-06-24 7:06 ` Glenn Morris
2015-06-24 7:52 ` Artur Malabarba
2015-06-24 13:36 ` Paul Eggert [this message]
2015-06-24 14:28 ` Artur Malabarba
2015-06-24 15:05 ` Eli Zaretskii
2015-06-24 15:19 ` Eli Zaretskii
2015-06-24 17:18 ` Artur Malabarba
2015-06-24 19:14 ` Eli Zaretskii
2015-06-24 20:05 ` Artur Malabarba
2015-06-24 23:17 ` Artur Malabarba
2015-06-24 23:37 ` Artur Malabarba
2015-06-25 15:03 ` Eli Zaretskii
2015-06-25 17:32 ` Artur Malabarba
2015-06-26 7:52 ` Eli Zaretskii
2015-06-26 11:41 ` Artur Malabarba
2015-06-26 13:32 ` Eli Zaretskii
2015-06-24 17:15 ` Glenn Morris
2015-06-24 17:38 ` Artur Malabarba
2015-06-24 15:55 ` Glenn Morris
2015-06-24 13:31 ` Paul Eggert
2015-06-24 15:58 ` Glenn Morris
2015-06-25 2:48 ` Paul Eggert
2015-06-25 23:21 ` Glenn Morris
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=558AB250.5040908@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=20887@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=rgm@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).