GNU bug report logs - #63225
Compiling regexp patterns (and REGEXP_CACHE_SIZE in search.c)

Previous Next

Full log

View this message in rfc822 format

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Mattias Engdegård <mattias.engdegard <at> gmail.com>
Cc: 63225 <at> debbugs.gnu.org
Subject: bug#63225: Compiling regexp patterns (and REGEXP_CACHE_SIZE in search.c)
Date: Tue, 09 May 2023 15:56:09 +0000

Mattias Engdegård <mattias.engdegard <at> gmail.com> writes:

> 9 maj 2023 kl. 14.02 skrev Ihor Radchenko <yantar92 <at> posteo.net>:
>
>> - forward-line + skip-chars-forward      :: (2.980 2 0.648)
>> - beginning-of-line + looking-at-p       :: (7.189 2 0.653)
>> - beginning-of-line + skip-chars-forward :: (6.833 2 0.634)
>> - forward-line + looking-at-p            :: (3.180 2 0.663)
>
> You may want to try the small improvement to skip-chars-forward that just arrived on master.

I did not get anything meaningful here. Likely because my benchmark is
not very stable (the above results did not stay the same for different
Emacs session for example, except relative numbers).

[in the same order]
(4.171 2 0.420)
(6.740 2 0.419)
(5.977 1 0.210)
(4.262 2 0.431)

>> May you elaborate what is the blocker then?
>
> Mostly time, but also coming up with a design that is compatible and reasonably future-safe, and convincing people that it's a good way forward (assuming it actually is). Emacs is a collaborative effort, after all.

Then it is not a blocker, but rather "let's discuss it first in a
dedicated, clearly marked thread".

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
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>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.