Upgrade to pcre2 version 10.32.
Bug: N/A
Test: builds and boots, getprop -Z works
Change-Id: Ib5592447c603a46fe03d71b412db58e46bad8e52
diff --git a/dist2/HACKING b/dist2/HACKING
index d727add..f99616a 100644
--- a/dist2/HACKING
+++ b/dist2/HACKING
@@ -256,6 +256,7 @@
values (which should match with the length):
META_MARK (*MARK:xxxx)
+META_COMMIT_ARG )*COMMIT:xxxx)
META_PRUNE_ARG (*PRUNE:xxx)
META_SKIP_ARG (*SKIP:xxxx)
META_THEN_ARG (*THEN:xxxx)
@@ -348,7 +349,7 @@
others) may be changed in the middle of patterns by items such as (?i). Their
processing is handled entirely at compile time by generating different opcodes
for the different settings. The runtime functions do not need to keep track of
-an options state.
+an option's state.
PCRE2_DUPNAMES, PCRE2_EXTENDED, PCRE2_EXTENDED_MORE, and PCRE2_NO_AUTO_CAPTURE
are tracked and processed during the parsing pre-pass. The others are handled
@@ -370,7 +371,7 @@
only be 4. The 8-bit library can be compiled to used 3-byte or 4-byte values,
and the 16-bit library can be compiled to use 4-byte values, though this
impairs performance. Specifing a LINK_SIZE larger than 2 for these libraries is
-necessary only when patterns whose compiled length is greater than 64K code
+necessary only when patterns whose compiled length is greater than 65535 code
units are going to be processed. When a LINK_SIZE value uses more than one code
unit, the most significant unit is first.
@@ -382,7 +383,7 @@
Opcodes with no following data
------------------------------
-These items are all just one unit long
+These items are all just one unit long:
OP_END end of pattern
OP_ANY match any one character other than newline
@@ -430,14 +431,22 @@
(PCRE2_ALLOW_EMPTY_CLASS is set).
-Backtracking control verbs with optional data
----------------------------------------------
+Backtracking control verbs
+--------------------------
-(*THEN) without an argument generates the opcode OP_THEN and no following data.
-OP_MARK is followed by the mark name, preceded by a length in one code unit,
-and followed by a binary zero. For (*PRUNE), (*SKIP), and (*THEN) with
-arguments, the opcodes OP_PRUNE_ARG, OP_SKIP_ARG, and OP_THEN_ARG are used,
-with the name following in the same format as OP_MARK.
+Verbs with no arguments generate opcodes with no following data (as listed
+in the section above).
+
+(*MARK:NAME) generates OP_MARK followed by the mark name, preceded by a
+length in one code unit, and followed by a binary zero. The name length is
+limited by the size of the code unit.
+
+(*ACCEPT:NAME) and (*FAIL:NAME) are compiled as (*MARK:NAME)(*ACCEPT) and
+(*MARK:NAME)(*FAIL) respectively.
+
+For (*COMMIT:NAME), (*PRUNE:NAME), (*SKIP:NAME), and (*THEN:NAME), the opcodes
+OP_COMMIT_ARG, OP_PRUNE_ARG, OP_SKIP_ARG, and OP_THEN_ARG are used, with the
+name following in the same format as for OP_MARK.
Matching literal characters
@@ -764,7 +773,7 @@
bracket from the start of the whole pattern. OP_RECURSE is also used for
"subroutine" calls, even though they are not strictly a recursion. Up till
release 10.30 recursions were treated as atomic groups, making them
-incompatible with Perl (but PCRE had then well before Perl did). From 10.30,
+incompatible with Perl (but PCRE had them well before Perl did). From 10.30,
backtracking into recursions is supported.
Repeated recursions used to be wrapped inside OP_ONCE brackets, which not only
@@ -814,4 +823,4 @@
opcode are the correct length, in order to catch updating errors.
Philip Hazel
-21 April 2017
+20 July 2018