all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, mattiase@acm.org, arstoffel@gmail.com,
	eller.helmut@gmail.com, dmcc2@hypnicjerk.ai,
	pipcet@protonmail.com, emacs-devel@gnu.org, acorallo@gnu.org,
	stefankangas@gmail.com
Subject: Re: [PATCH] add compiled regexp primitive lisp object
Date: Mon, 23 Dec 2024 17:10:34 +0000	[thread overview]
Message-ID: <87seqejpf9.fsf@localhost> (raw)
In-Reply-To: <868qs64a65.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> 1. They could be inspected from Elisp, and hopefully optimized
>>    better. For now, there is simply no way to detect which parts of
>>    regexps are slow and which are not.
>
> If we can optimize them from Lisp, we should be able to do the same in
> C.  If you explain what kind of optimization opportunities you had in
> mind, we could discuss how to implement that.  In any case, adding
> APIs for regexp optimizations doesn't require to have compiled regexp
> objects.

What I had in mind is some kind of profiler for regexps.  I cannot
imagine such a profiler without having access to the state machine
instructions emitted by regexp compiler - there will be no easy mapping
between regexp itself and the resulting compiled instructions (that
mapping will depend on the specifics of Emacs compiler)

>> 2. They could maybe even be constructed from Elisp, opening
>>    opportunities for custom regexp compilers that can be tailored to
>>    specific application needs rather than having to stick to hard-coded
>>    generic tradeoffs Emacs has to do without knowing the purpose of a
>>    regexp.
>
> How will this help making matching faster, and why does this have to
> be via compiled regexp objects?

My motivation is
https://burntsushi.net/regex-internals/#literal-extraction that explains
how regexp compilation depends on certain heuristics.

For example, when searching for "\\(foo\\|bar\\)[a-z]+", heuristics
invoking simple string literal search for "foo" and "bar" first before
using heavy regexp automata is justified. Not so much when the prefix is
simply " " that usually occurs very frequently in text.

However, for specially structures texts (e.g. in parsers), additional
knowledge about structure is available and can be utilized to fine-tune
the regexp compilation.

Ultimately, an ability to construct instructions from scratch can be
useful - this may allow going beyond what Emacs regexp syntax provides;
and faster.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2024-12-23 17:10 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  5:08 [PATCH] add compiled regexp primitive lisp object Danny McClanahan
2024-07-30 13:02 ` Philip Kaludercic
2024-07-31 22:33   ` dmcc2
2024-08-01  1:04 ` Pip Cet
2024-08-04 23:38   ` Danny McClanahan
2024-08-05  3:47     ` dmcc2
2024-08-05  4:39   ` Danny McClanahan
2024-08-05  7:15     ` Danny McClanahan
2024-08-05 17:55     ` Pip Cet
2024-08-06 15:15       ` Danny McClanahan
2024-08-06 15:57         ` Eli Zaretskii
2024-08-07  4:28           ` Danny McClanahan
2024-08-06 18:18         ` Pip Cet
2024-08-06 18:38           ` Eli Zaretskii
2024-08-07  4:23             ` Danny McClanahan
2024-08-07 12:00               ` Eli Zaretskii
2024-08-07 12:43                 ` Helmut Eller
2024-08-07 13:40                   ` Augusto Stoffel
2024-08-07 15:23                     ` Danny McClanahan
2024-08-14  1:32                     ` Stefan Monnier
2024-11-26 18:05                       ` Danny McClanahan
2024-11-26 18:50                         ` Danny McClanahan
2024-12-08 15:24                         ` Danny McClanahan
2024-12-09 15:12                           ` Stefan Monnier
2024-12-09 15:13                             ` Stefan Monnier
2024-12-22 19:14                       ` Ihor Radchenko
2024-12-22 19:24                         ` Eli Zaretskii
2024-12-22 20:02                           ` Ihor Radchenko
2024-12-22 20:20                             ` Eli Zaretskii
2024-12-22 20:31                               ` Ihor Radchenko
2024-12-23 13:38                                 ` Björn Bidar
     [not found]                                 ` <8634ie60jd.fsf@gnu.org>
2024-12-23 16:33                                   ` Ihor Radchenko
2024-12-23 16:49                                     ` Eli Zaretskii
2024-12-23 17:10                                       ` Ihor Radchenko [this message]
2024-12-24 21:16                                         ` Björn Bidar
2024-12-24  5:37                                     ` Stefan Monnier
2024-12-24  9:30                                       ` Ihor Radchenko
2024-12-24 15:14                                         ` Stefan Monnier
2024-08-07 15:02                 ` Danny McClanahan
2024-08-07 15:23                   ` Eli Zaretskii
2024-08-14  1:25               ` Stefan Monnier
2024-08-07  7:59           ` Danny McClanahan
2024-08-06 12:08     ` Eli Zaretskii
2024-08-01  8:30 ` Andrea Corallo
2024-08-01 10:06   ` Gerd Möllmann
2024-08-06 13:47   ` Danny McClanahan
2024-08-06 13:57     ` Danny McClanahan
2024-08-07  7:21     ` Andrea Corallo
2024-08-07  8:27       ` Danny McClanahan

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=87seqejpf9.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=acorallo@gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=dmcc2@hypnicjerk.ai \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pipcet@protonmail.com \
    --cc=stefankangas@gmail.com \
    /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.