all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: 65250@debbugs.gnu.org
Subject: bug#65250: 30.0.50; "C-h f" is much slower on the master branch
Date: Mon, 14 Aug 2023 18:11:42 +0300	[thread overview]
Message-ID: <834jl1bqvl.fsf@gnu.org> (raw)
In-Reply-To: <yp1a5utbrst.fsf@fencepost.gnu.org> (message from Andrea Corallo on Mon, 14 Aug 2023 10:51:46 -0400)

> From: Andrea Corallo <acorallo@gnu.org>
> Cc: 65250@debbugs.gnu.org
> Date: Mon, 14 Aug 2023 10:51:46 -0400
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > So I think the patch I presented in my original report is exactly what
> > is needed here: the problem only happens in builds without
> > native-compilation, and in that case there's no reason whatsoever to
> > call comp-function-type-spec.  (And builds from a release tarball will
> > not see that problem, since the tarball comes with byte-compiled
> > comp.el and comp-cstr.el.)
> >
> > Do you agree?
> 
> I certainly do.  Thanks for the anylysis and the patch!

Installed.

Btw, why aren't comp.el and comp-cstr.el byte-compiled in a build
without native-compilation?  That's probably a bug in itself: we
generally byte-compile all the *.el files, even those that are not
relevant to the configuration being built.





  reply	other threads:[~2023-08-14 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12 15:49 bug#65250: 30.0.50; "C-h f" is much slower on the master branch Eli Zaretskii
2023-08-12 16:57 ` Andrea Corallo
2023-08-12 17:23   ` Eli Zaretskii
2023-08-14  8:59 ` Andrea Corallo
2023-08-14 12:19   ` Eli Zaretskii
2023-08-14 14:40     ` Eli Zaretskii
2023-08-14 14:51       ` Andrea Corallo
2023-08-14 15:11         ` Eli Zaretskii [this message]
2023-08-14 15:19           ` Andrea Corallo
2023-08-14 15:45             ` Andrea Corallo
2023-08-16  8:37               ` Andrea Corallo
2023-08-16 13:12                 ` Eli Zaretskii
2023-08-16 13:55                   ` Andrea Corallo
2023-08-16 14:52                     ` Eli Zaretskii

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=834jl1bqvl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65250@debbugs.gnu.org \
    --cc=acorallo@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 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.