After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 679155 - support using the PCRE JIT
support using the PCRE JIT
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gregex
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on: 689791
Blocks:
 
 
Reported: 2012-06-29 18:09 UTC by Christian Persch
Modified: 2018-05-24 14:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Persch 2012-06-29 18:09:35 UTC 
Latest PCRE supports JIT code generation to speed up matching (at the expense of slower g_regex_new()).

See http://sljit.sourceforge.net/pcre.html and http://sljit.sourceforge.net/regex_perf.html for some data on the performance of JITing vs. the interpreter.

Pushed a proposal to the wip/pcre-jit branch.
Comment 1 Matthias Clasen 2012-06-30 05:07:11 UTC 
One question I had on that proposal is:

Why would you ever want to call g_match_info_get_jited ?

All your other pcre branches looked good to me, btw.
There were some small typos here and there that I'd rather comment on in splinter.
Comment 2 Christian Persch 2012-06-30 13:16:00 UTC 
Hmm you're right, there's no use for it :-) I should just add the list of things in the pattern that will make pcre not support jiting to our docs.
Comment 3 GNOME Infrastructure Team 2018-05-24 14:19:37 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/566.