From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: C and Emacs Lisp code parts
Date: Sat, 2 Jul 2016 16:41:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20160702T183356-429@post.gmane.org> (raw)
In-Reply-To: 83mvm1tg0g.fsf@gnu.org
Eli Zaretskii <eliz <at> gnu.org> writes:
> As for font-lock, its features are based on regular expression and
> syntax tables, both of which are implemented in C as well.
The fact that regexp are implemented in C is not a guarantee of
the best speed.
Some years ago, when the Common Lisp CL-PPCRE library appeared,
it was benchmarked 5-20 times faster than C regexp libraries, because
the automaton was compiled directly to machine code, whereas the C
counterpart had to do lookups into the table that describes the
automaton.
I am no specialist of the the current variants of regexp libraries
but some of them seem to make use of jit compiler.
(See http://sljit.sourceforge.net/regex_perf.html for example)
So isnt't there some response time to gain around regexps?
Because I don't see that src/regex.c is using a jit.
Fabrice
next prev parent reply other threads:[~2016-07-02 16:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 8:03 C and Emacs Lisp code parts Andreas Röhler
2016-07-01 8:13 ` Eli Zaretskii
2016-07-01 8:39 ` Andreas Röhler
2016-07-01 9:16 ` Alan Mackenzie
2016-07-01 12:07 ` Andreas Röhler
2016-07-01 13:04 ` Eli Zaretskii
2016-07-05 22:48 ` John Wiegley
2016-07-06 7:25 ` Andreas Röhler
2016-07-06 7:31 ` Andreas Röhler
2016-07-06 15:27 ` Phillip Lord
2016-07-01 9:17 ` John Wiegley
2016-07-01 13:26 ` Andreas Röhler
2016-07-01 9:25 ` Eli Zaretskii
2016-07-01 12:25 ` Andreas Röhler
2016-07-01 13:01 ` Eli Zaretskii
2016-07-01 13:05 ` Andy Moreton
2016-07-01 15:14 ` Karl Fogel
2016-07-01 16:52 ` Andreas Röhler
2016-07-01 17:13 ` Eli Zaretskii
2016-07-01 17:36 ` Andreas Röhler
2016-07-01 17:38 ` Eli Zaretskii
2016-07-02 16:41 ` Fabrice Popineau [this message]
2016-07-02 17:16 ` Eli Zaretskii
2016-07-01 17:55 ` Alan Mackenzie
2016-07-01 18:31 ` Andreas Röhler
2016-07-01 18:57 ` Alan Mackenzie
2016-07-01 20:04 ` Andreas Röhler
2016-07-01 20:31 ` Davis Herring
2016-07-02 6:34 ` Andreas Röhler
2016-07-02 11:29 ` Paul Eggert
2016-07-05 17:02 ` Davis Herring
2016-07-05 19:35 ` Andreas Röhler
2016-07-02 6:32 ` Eli Zaretskii
2016-07-02 7:01 ` Andreas Röhler
2016-07-02 8:15 ` Eli Zaretskii
2016-07-02 3:32 ` Tom Tromey
2016-07-02 3:42 ` Clément Pit--Claudel
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=loom.20160702T183356-429@post.gmane.org \
--to=fabrice.popineau@gmail.com \
--cc=emacs-devel@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 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).