From: Eli Zaretskii <eliz@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 51734@debbugs.gnu.org
Subject: bug#51734: 29.0.50; got slow
Date: Thu, 11 Nov 2021 10:09:30 +0200 [thread overview]
Message-ID: <83pmr715c5.fsf@gnu.org> (raw)
In-Reply-To: <b4mbl2rcsyv.fsf@jpl.org> (message from Katsumi Yamaoka on Thu, 11 Nov 2021 11:43:36 +0900)
> Date: Thu, 11 Nov 2021 11:43:36 +0900
> From: Katsumi Yamaoka <yamaoka@jpl.org>
> Cc: 51734@debbugs.gnu.org
>
> On Wed, 10 Nov 2021 16:08:09 +0200, Eli Zaretskii wrote:
> > Building Emacs with -O0 should never make Emacs so slow as described
> > by the OP. Disabling optimizations generally makes Emacs about 2.5 to
> > 3 times slower, but that's still a far cry from response time of a
> > second or two to C-s.
>
> Yes, I have no problem with -O0 on Emacs master till last week
> and also on 28, 27, 26.
Can you be more specific regarding which commit was the last one where
the problem didn't exist?
> Probably what I should do could be bisecting the recent commits.
That'd be best, if you can. Thanks.
next prev parent reply other threads:[~2021-11-11 8:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 0:36 bug#51734: 29.0.50; got slow Katsumi Yamaoka
2021-11-10 12:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 14:08 ` Eli Zaretskii
2021-11-10 12:53 ` Eli Zaretskii
2021-11-11 2:43 ` Katsumi Yamaoka
2021-11-11 8:09 ` Eli Zaretskii [this message]
2021-11-11 12:02 ` Katsumi Yamaoka
2021-11-11 14:15 ` Eli Zaretskii
2021-11-11 18:11 ` Ken Brown
2021-11-11 18:33 ` Ken Brown
2021-11-11 18:42 ` Eli Zaretskii
2021-11-11 19:28 ` Ken Brown
2021-11-11 20:17 ` Ken Brown
2021-11-11 20:20 ` Eli Zaretskii
2021-11-11 20:30 ` Ken Brown
2021-11-11 20:36 ` Eli Zaretskii
2021-11-11 23:45 ` Katsumi Yamaoka
2021-11-12 18:22 ` Ken Brown
2021-11-12 19:26 ` Eli Zaretskii
2021-11-12 20:06 ` Ken Brown
2021-11-14 1:13 ` Lars Ingebrigtsen
2021-11-14 15:42 ` Ken Brown
2021-11-14 17:58 ` Lars Ingebrigtsen
2021-11-14 19:11 ` Ken Brown
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pmr715c5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51734@debbugs.gnu.org \
--cc=yamaoka@jpl.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.