unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: yamaoka@jpl.org, 51734@debbugs.gnu.org
Subject: bug#51734: 29.0.50; got slow
Date: Wed, 10 Nov 2021 16:08:09 +0200	[thread overview]
Message-ID: <83wnlg2jee.fsf@gnu.org> (raw)
In-Reply-To: <878rxw5gon.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)

> Cc: 51734@debbugs.gnu.org
> Date: Wed, 10 Nov 2021 20:38:32 +0800
> From:  Po Lu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> > For instance, the cursor moves not smoothly while repeating `C-n's,
> > `C-s' takes a couple of seconds for the text searched to appear, etc.
> > It should have happened after my build on Thu 4 Nov 22:00 UTC
> > through the previous build on Mon 8 Nov 22:00 UTC.
> >
> > Thanks.
> 
> See below.
> 
> >  'configure 'CFLAGS=-O0 -g3' --verbose --with-x-toolkit=gtk3
> >  --with-imagemagick'
> 
> Did you notice the problem in the Emacs in which you ran
> `report-emacs-bug'?  `-O0 -g3' will normally slow down Emacs
> considerably, as it disables all compiler optimizations, and is used as
> a debugging aid.

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.

I use unoptimized builds of the development version all the time,
because optimized builds are very hard to debug.





  reply	other threads:[~2021-11-10 14:08 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 [this message]
2021-11-10 12:53 ` Eli Zaretskii
2021-11-11  2:43   ` Katsumi Yamaoka
2021-11-11  8:09     ` Eli Zaretskii
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

  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=83wnlg2jee.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51734@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --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 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).