From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <ghe@sdf.org>
Cc: rudalics@gmx.at, stephen.berman@gmx.net, acm@muc.de, emacs-devel@gnu.org
Subject: Re: The Emacs master is much slower than the emacs-27 branch.
Date: Sat, 05 Dec 2020 17:55:32 +0200 [thread overview]
Message-ID: <83wnxwb62z.fsf@gnu.org> (raw)
In-Reply-To: <alpine.NEB.2.22.394.2012051457440453.882@sdf.lonestar.org> (message from Gregory Heytings on Sat, 05 Dec 2020 15:17:34 +0000)
> Date: Sat, 05 Dec 2020 15:17:34 +0000
> From: Gregory Heytings <ghe@sdf.org>
> cc: rudalics@gmx.at, stephen.berman@gmx.net, emacs-devel@gnu.org, acm@muc.de
>
> >> I'd guess that Eli will merge b9b32074cecb0e0d20cf527eadacbb0b7f5cced9
> >> into emacs-27 very soon after the Emacs 27.2 release
> >
> > No, this is unlikely to happen. The emacs-27 branch should only get
> > safe bugfixes at this time.
>
> I did not know that an Emacs 27.3 release was not planned.
I didn't say it wasn't. (We won't consider whether 27.3 should be
released until some time after releasing 27.2, based on the bugs and
regressions that will still be reported against the emacs-27 branch.)
However, whether there will be Emacs 27.3 or not, the emacs-27 branch,
like any other release branch, should only get changes that fix bugs
and aren't too risky (i.e. cannot cause additional bugs/issues).
> In that case, the emacs-27 branch will forever remain slower with
> -Og and -O0 (at least on GNU/Linux 64-bit platforms with GCC).
Yes. And that is not so bad, given that your timings indicate Emacs
27.1 compiled with optimizations is better than Emacs 25 and only
slightly slower than Emacs 26.
next prev parent reply other threads:[~2020-12-05 15:55 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 18:15 The Emacs master is much slower than the emacs-27 branch Alan Mackenzie
2020-12-03 20:17 ` Eli Zaretskii
2020-12-04 9:13 ` Alan Mackenzie
2020-12-03 20:59 ` Mattias Engdegård
2020-12-04 9:24 ` Alan Mackenzie
2020-12-04 10:46 ` Alan Third
2020-12-04 11:07 ` Mattias Engdegård
2020-12-03 21:09 ` Ergus
2020-12-04 9:19 ` Alan Mackenzie
2020-12-03 22:17 ` Stephen Berman
2020-12-04 9:04 ` Alan Mackenzie
2020-12-04 9:32 ` Stephen Berman
2020-12-04 9:53 ` Alan Mackenzie
2020-12-04 10:14 ` Stephen Berman
2020-12-04 11:45 ` Eli Zaretskii
2020-12-04 12:54 ` Stephen Berman
2020-12-04 13:28 ` Eli Zaretskii
2020-12-04 13:53 ` Stephen Berman
2020-12-04 14:05 ` Stephen Berman
2020-12-04 15:51 ` Eli Zaretskii
2020-12-04 16:03 ` Stephen Berman
2020-12-04 16:28 ` Óscar Fuentes
2020-12-04 18:51 ` Eli Zaretskii
2020-12-04 21:37 ` Stephen Berman
2020-12-05 8:05 ` Eli Zaretskii
2020-12-04 16:49 ` Stefan Monnier
2020-12-05 14:04 ` Basil L. Contovounesios
2020-12-05 14:38 ` Stefan Monnier
[not found] ` <837dpxedmz.fsf@gnu.org>
2020-12-04 17:03 ` Stephen Berman
2020-12-04 17:59 ` Stephen Berman
2020-12-04 20:47 ` Óscar Fuentes
2020-12-04 21:33 ` Stephen Berman
2020-12-04 17:07 ` Eli Zaretskii
2020-12-04 19:27 ` Gregory Heytings via Emacs development discussions.
2020-12-04 19:34 ` Stephen Berman
2020-12-04 19:58 ` Eli Zaretskii
2020-12-04 20:33 ` Gregory Heytings via Emacs development discussions.
2020-12-04 20:47 ` Eli Zaretskii
2020-12-04 20:59 ` Gregory Heytings via Emacs development discussions.
2020-12-04 21:02 ` Eli Zaretskii
2020-12-04 21:20 ` Gregory Heytings via Emacs development discussions.
2020-12-05 7:44 ` Eli Zaretskii
2020-12-05 8:14 ` Gregory Heytings via Emacs development discussions.
2020-12-05 8:44 ` Gregory Heytings via Emacs development discussions.
2020-12-05 9:14 ` Eli Zaretskii
2020-12-05 9:20 ` Eli Zaretskii
2020-12-05 9:33 ` Eli Zaretskii
2020-12-05 13:50 ` Basil L. Contovounesios
2020-12-05 14:29 ` Eli Zaretskii
2020-12-05 14:56 ` Ergus
2020-12-05 15:14 ` Eli Zaretskii
2020-12-05 15:29 ` Andrea Corallo via Emacs development discussions.
2020-12-05 15:15 ` Gregory Heytings via Emacs development discussions.
2020-12-05 15:31 ` Óscar Fuentes
2020-12-05 9:05 ` Eli Zaretskii
2020-12-05 9:23 ` martin rudalics
2020-12-05 12:55 ` Gregory Heytings via Emacs development discussions.
2020-12-05 13:41 ` Eli Zaretskii
2020-12-05 15:17 ` Gregory Heytings via Emacs development discussions.
2020-12-05 15:55 ` Eli Zaretskii [this message]
2020-12-05 14:47 ` Óscar Fuentes
2020-12-05 15:07 ` martin rudalics
2020-12-05 15:24 ` Gregory Heytings via Emacs development discussions.
2020-12-05 15:36 ` martin rudalics
2020-12-05 15:39 ` Gregory Heytings via Emacs development discussions.
2020-12-05 15:47 ` Óscar Fuentes
2020-12-05 17:21 ` Gregory Heytings via Emacs development discussions.
2020-12-05 15:57 ` Eli Zaretskii
2020-12-05 16:04 ` Gregory Heytings via Emacs development discussions.
2020-12-05 15:08 ` Eli Zaretskii
2020-12-04 14:55 ` Arthur Miller
2020-12-04 15:00 ` Arthur Miller
2020-12-04 9:59 ` Gregory Heytings via Emacs development discussions.
2020-12-09 4:23 ` andres.ramirez
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=83wnxwb62z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=ghe@sdf.org \
--cc=rudalics@gmx.at \
--cc=stephen.berman@gmx.net \
/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).