Ævar Arnfjörð Bjarmason writes:
> I am very tempted though to support them in parallel, if only for ease
> of performance testing and to be able to roll out support for
> grep.patternType=perl meaning pcre1 for now, but add a
> grep.patternType=pcre2 for testing (and make
Jeffrey Walton writes:
>> Just to make sure that we are on the same page. While I do not see
>> the need to link with both variants and allow users to choose
>> between them at runtime, I do not know if the whole world is ready
>> to drop pcre1 and use pcre2 (the latter of
> Just to make sure that we are on the same page. While I do not see
> the need to link with both variants and allow users to choose
> between them at runtime, I do not know if the whole world is ready
> to drop pcre1 and use pcre2 (the latter of which has only been
> around for a bit over two
On Sat, Apr 1, 2017 at 8:24 PM, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason writes:
>
>> On Sat, Apr 1, 2017 at 12:48 AM, Junio C Hamano wrote:
>>> Ævar Arnfjörð Bjarmason writes:
>>>
That enables the new JIT
Ævar Arnfjörð Bjarmason writes:
> On Sat, Apr 1, 2017 at 12:48 AM, Junio C Hamano wrote:
>> Ævar Arnfjörð Bjarmason writes:
>>
>>> That enables the new JIT support in pcre v2:
>>>
>>> s/iterrx fixed prx
>>> rx 2.19--
On Sat, Apr 1, 2017 at 12:48 AM, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason writes:
>
>> That enables the new JIT support in pcre v2:
>>
>> s/iterrx fixed prx
>> rx 2.19-- -33% -44%
>> fixed 1.47 49%-- -17%
>> prx 1.22
Ævar Arnfjörð Bjarmason writes:
> That enables the new JIT support in pcre v2:
>
> s/iterrx 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
The recent libpcre2 got me interested in seeing what the difference in
v1 and v2 was.
So I hacked up a *very basic* patch for libpcre2 that passes all
tests, but obviously isn't ready for inclusion (I searched/replaced
all the v1 usage with v2). I'm not even bothering sending this to the
list
8 matches
Mail list logo