Add pcre_get_compiled_regex_cache_ex() with local_aware flag

A new function `pcre_get_compiled_regex_cache_ex()` is introduced,
which allows to compile regexp pattern using the "C" local

Add pcre_get_compiled_regex_cache_ex() with local_aware flag

A new function `pcre_get_compiled_regex_cache_ex()` is introduced,
which allows to compile regexp pattern using the "C" locale instead
of a current locale.

This will be needed to replace setlocale() usage in fileinfo,
which is not thread-safe.

show more ...

Accept null for preg_quote delimiter argument

Related to bug #78163.

Fix #77827: preg_match does not ignore \r in regex flags

Fixed possible incorrect "mark" usage

year++

year++

Fix yet one data race in PCRE

PCRE 8.x initializes the pattern compiler on demand during the first
pcre_study call. It could be worse, but since the compiled patterns are
cached, the

Fix yet one data race in PCRE

PCRE 8.x initializes the pattern compiler on demand during the first
pcre_study call. It could be worse, but since the compiled patterns are
cached, the locking impact is minimal. PCRE 10.x always compiles the
pattern and thread sanitizer doesn't complain about the compiler
initialization, thus the newer PCRE version seems to be unafected.

show more ...

Fix use after free revealed by phpdbg

Fixed bug #75601 Thread race in PCRE JIT support

Fixed bug #75601 Thread race in PCRE JIT support

Fixed #75539 and #74183 - preg_last_error not returning error code after error

Fix UTF check in pcre_grep

In this case it loops through different subjects without looking for sub
matches and matches are done against the same pattern. Thus, don't reset
the UTF c

Fix UTF check in pcre_grep

In this case it loops through different subjects without looking for sub
matches and matches are done against the same pattern. Thus, don't reset
the UTF check flag but use it to check whether JIT should be used and
otherwise let PCRE to do the job according to what was saved into the
pattern.

show more ...

Fix uninitialized flag when JIT is disabled

Fixed bug #75089 (preg_grep() is not reporting PREG_BAD_UTF8_ERROR after first input string)

Upgrade bundled PCRE to 8.41

HEADSUP! With PCRE 8.39 the JIT related code was changed in the way,
that additional valgrind options became almost unavoidable. Valgrind
had it already

Upgrade bundled PCRE to 8.41

HEADSUP! With PCRE 8.39 the JIT related code was changed in the way,
that additional valgrind options became almost unavoidable. Valgrind
had it already sometimes hard with JIT, now there are seem to be more
cases requiring special valgrind options.

For this reason, the new configure option --with-pcre-valgrind was
introduced. The option is development/debugging only and turns on the
Valgrind related pieces in PCRE, so then false positives are avoided
to the big part. In addition, run-tests.php was added a new valgrind
option, when the leak check is enabled and the test filepath contains
pcre.

Thus, to debug the code related to PCRE with JIT enabled, two things
would likely make sense

- configure --with-pcre-valgrind
- valgrind option --smc-check=all if run-tests.php is not used

The checks so far reveal no new issues.

show more ...

Fixed bug #74873 (Minor BC break: PCRE_JIT changes output of preg_match()).

Avoid string duplication in preg_split()

Only compute callback name in error cases

Mostly the callback name is only used to report an error. Try to
avoid calculating it if no error occurred.

preg_replace() optimization

Avoid string reallocations in preg_quote()

PCRE_EXTRA_MARK is useful only for preg_replace_callbakc().
Removed branch expectations.

Added support for PCRE JIT fast path API

Avoid double copying

Don't allocate empty strings, use single interned string instead.

add PREG_UNMATCHED_AS_NULL flag to allow distinguish between unmatched subpatterns and empty matches