From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 20887@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#20887: 'make bootstrap' now verrrry slow due to recent isearch changes
Date: Wed, 24 Jun 2015 08:52:15 +0100 [thread overview]
Message-ID: <CAAdUY-JccFPdWeodbZj1rXHJgEkwtsa7CViZeA97Qniw8Lg2uA@mail.gmail.com> (raw)
In-Reply-To: <2nbng5pou7.fsf@fencepost.gnu.org>
I don't know. Frankly, a bootstrap of 5 min seems incredibly fast, :)
mine always takes at least 10.
When I reporte the change added 5 sec to compile time, I was testing
the following:
(benchmark-run 1 (byte-compile-file (buffer-file-name)))
which reports 3.13 seconds for me.
Does anyone know what could cause these 4 seconds to become 5 min
during bootstrap?
Does bootstrap compile the file 60 times? =P
If botstrap loads that code without compiling first, then it could
take about 10 seconds, but that still doesn't account for so much.
2015-06-24 8:06 GMT+01:00 Glenn Morris <rgm@gnu.org>:
> Paul Eggert wrote:
>
>> When I run 'make bootstrap' now it's veerrrrry slow, hanging after this output:
>>
>> ...
>> Reloading stale subr-x.el
>> Loading /home/eggert/src/gnu/emacs/tmn/lisp/emacs-lisp/subr-x.el (source)...
>> Reloading stale isearch.el
>> Loading /home/eggert/src/gnu/emacs/tmn/lisp/isearch.el (source)...
>
> How can a bootstrap have stale files...? Mine doesn't.
> But yes, dumping bootstrap-emacs is now ridiculously slow (~ 5 minutes).
> I would like to know where Artur bought his laptop [1], which by my
> estimate must run at about 200GHz.
>
> [1] http://lists.gnu.org/archive/html/emacs-devel/2015-06/msg00426.html
next prev parent reply other threads:[~2015-06-24 7:52 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 [this message]
2015-06-24 13:36 ` Paul Eggert
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=CAAdUY-JccFPdWeodbZj1rXHJgEkwtsa7CViZeA97Qniw8Lg2uA@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=20887@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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).