[PATCH] grep: use custom JIT stack with pcre2

2019-07-21 Thread Carlo Marcelo Arenas Belón
94da9193a6 ("grep: add support for PCRE v2", 2017-06-01) allocate a stack and assign it to a match context, but never pass it to pcre2_jit_match, using instead the default. Signed-off-by: Carlo Marcelo Arenas Belón --- This might have positive performance consequences (per the comments) but haven

Re: [PATCH] grep: skip UTF8 checks explicitally

2019-07-21 Thread Eric Sunshine
On Sun, Jul 21, 2019 at 2:31 PM Carlo Marcelo Arenas Belón wrote: > grep: skip UTF8 checks explicitally s/explicitally/explicitly/ > Usually PCRE is compiled with JIT support, and therefore the code > path used includes calling pcre2_jit_match (for PCRE2), that ignores > invalid UTF-8 in the cor

[PATCH] grep: skip UTF8 checks explicitally

2019-07-21 Thread Carlo Marcelo Arenas Belón
Usually PCRE is compiled with JIT support, and therefore the code path used includes calling pcre2_jit_match (for PCRE2), that ignores invalid UTF-8 in the corpus. Make that option explicit so it can be also used when JIT is not enabled and pcre2_match is called instead, preventing `git grep` to a

[PATCH v1 1/1] pack-refs: pack expired loose refs to packed_refs

2019-07-21 Thread 16657101987
From: Sun Chao When a packed ref is deleted, the whole packed-refs file is rewrite and omit the ref that no longer exists. However if another gc command is running and call `pack-refs --all` simultaneously, there is a change that a ref just updated will lost the newly commits. Through these step

[PATCH v1 0/1] pack-refs: pack expired loose refs to packed_refs

2019-07-21 Thread 16657101987
From: Sun Chao When a packed ref is deleted, the whole packed-refs file is rewrite and omit the ref that no longer exists. However if another gc command is running and call `pack-refs --all` simultaneously, there is a change that a ref just updated will lost the newly commits. There are two vali

Git Test Coverage Report (July 21)

2019-07-21 Thread Derrick Stolee
Here is today's test coverage report. If anyone is interested, I now also have a way to generate these reports based on a topic branch on any public Git repo. Let me know if you would like me to run a build and give you the text report directly. I've used it myself for work in progress before su