unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Juri Linkov <juri@linkov.net>,
	 emacs-devel@gnu.org,  Andrea Corallo <akrl@sdf.org>
Subject: Re: Native compilation of Keyboard Macros
Date: Sat, 17 Sep 2022 23:12:51 -0400	[thread overview]
Message-ID: <jwvr109xtrd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87fsgpg49a.fsf@posteo.net> (Philip Kaludercic's message of "Sat,  17 Sep 2022 20:00:49 +0000")

> OK, but wouldn't that exclude the possibility of it being compiled,
> *unless* there were some way to translate the rest of the input into
> something else.

You can't "transparently" compile them, no.  But the user can ask
explicitly for a kind of "snapshot": compile them to the code
executed for a particular run of that keyboard macro.

In any case, as for all optimization problems, I'd start by
investigating your very concrete example to try and figure exactly where
the time is spent.  Else, you may end up missing the important spot.


        Stefan




  reply	other threads:[~2022-09-18  3:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 18:56 Native compilation of Keyboard Macros Philip Kaludercic
2022-09-16 19:27 ` Stefan Monnier
2022-09-17 17:52   ` Juri Linkov
2022-09-17 18:26     ` Philip Kaludercic
2022-09-17 18:40       ` Juri Linkov
2022-09-17 20:00         ` Philip Kaludercic
2022-09-18  3:12           ` Stefan Monnier [this message]
2022-09-18  5:02   ` Visuwesh
2022-09-18 13:46     ` Stefan Monnier
2022-09-16 19:54 ` Óscar Fuentes
2022-09-17 14:49   ` Philip Kaludercic
2022-09-17 15:33     ` Óscar Fuentes

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=jwvr109xtrd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=akrl@sdf.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=philipk@posteo.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).