From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: 20887-done@debbugs.gnu.org, Artur Malabarba <bruce.connor.am@gmail.com>
Subject: bug#20887: 'make bootstrap' now verrrry slow due to recent isearch changes
Date: Wed, 24 Jun 2015 19:48:14 -0700 [thread overview]
Message-ID: <558B6BEE.4030500@cs.ucla.edu> (raw)
In-Reply-To: <wulhf9ayip.fsf@fencepost.gnu.org>
Glenn Morris wrote:
> No, because I do a proper bootstrap. Accept no imitations!:)
> There are no "stale" messages in such a build, and the isearch slowness
> only happens once.
OK. Still, running this from a fresh checkout:
./autogen.sh
./configure
make
also exhibited the "stale" messages and the extreme slowdown. So the problem
wasn't limited to my rm hack (which I do, by the way, because it's ordinarily
much faster than "make bootstrap").
Anyway, the performance bug seems to be fixed now -- thanks! -- so I'm marking
this as done.
next prev parent reply other threads:[~2015-06-25 2:48 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
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 [this message]
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=558B6BEE.4030500@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=20887-done@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).