From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Jeffrey Walton <noloader@gmail.com>
Subject: Re: Very promising results with libpcre2
Date: Sat, 1 Apr 2017 10:55:11 +0200 [thread overview]
Message-ID: <CACBZZX416M3YFDAACGAWCjJ4Xt0g78zpFF+iusMCarKb7SSfVw@mail.gmail.com> (raw)
In-Reply-To: <xmqqtw69vz9t.fsf@gitster.mtv.corp.google.com>
On Sat, Apr 1, 2017 at 12:48 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> That enables the new JIT support in pcre v2:
>>
>> s/iter rx fixed prx
>> rx 2.19 -- -33% -44%
>> fixed 1.47 49% -- -17%
>> prx 1.22 79% 20% --
>
> The numbers with JIT does look "interesting".
>
> I couldn't quite tell if there are major incompatibilities in the
> regex language itself between two versions from their documentation,
> but assuming that there isn't (modulo bugfixes and enhancements) and
> assuming that we are going to use their standard matcher, it may be
> OK to just use the newer one without linking both.
There's no incompatibilities in the regex language itself (modulo bugs
etc). So yeah, I'll prepare some patch to use v2.
next prev parent reply other threads:[~2017-04-01 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 21:23 Very promising results with libpcre2 Ævar Arnfjörð Bjarmason
2017-03-31 22:48 ` Junio C Hamano
2017-04-01 8:55 ` Ævar Arnfjörð Bjarmason [this message]
2017-04-01 18:24 ` Junio C Hamano
2017-04-01 19:11 ` Ævar Arnfjörð Bjarmason
2017-04-02 3:45 ` Junio C Hamano
2017-04-01 23:33 ` Jeffrey Walton
2017-04-02 3:45 ` Junio C Hamano
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=CACBZZX416M3YFDAACGAWCjJ4Xt0g78zpFF+iusMCarKb7SSfVw@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=noloader@gmail.com \
--cc=peff@peff.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.
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.