Re: [RFC/PATCH 7/7] grep: use PCRE v2 for optimized fixed-string search
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 27, 2019, 19:06 UTC
- Message-ID
- <xmqqv9wqalv2.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <nycvar.QRO.7.76.6.1906272042350.44@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 16 quoted lines
>> > > If we would not have plenty of exercise for the PCRE2 build options, I >> > > would be worried. But AFAICT the CI build includes this all the time, so >> > > we're fine. >> > >> > Well, I'd feel safer if it were not "all the time", i.e. we know we >> > are testing both sides of the coin. >> >> AFAIR at least the Linux32 job is built without PCRE2 by default. I might >> be wrong on that, though... > > Actually, it seems that _all_ of the Linux builds in our Azure Pipeline > compile without pcre2. It seems you have to pass `USE_LIBPCRE2=1` to > `make`, and we do not do that in `ci/run-build-and-tests.sh` nor in > `azure-pipelines.yml`. I do not even see that for the macOS builds. > > So we got PCRE2 covered only in the Windows build, it seems.
OK, it sounds like we have sufficient coverage on both fronts. Good.