ViewVC logotype

Diff of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 836 by ph10, Wed Dec 28 17:16:11 2011 UTC revision 1587 by zherczeg, Sat Aug 8 06:02:16 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.30  Note that the PCRE 8.xx series (PCRE1) is now in a bugfix-only state. All
5  ------------  development is happening in the PCRE2 10.xx series.
7  1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this  Version 8.38 xx-xxx-xxxx
8      name is defined in ctype.h.  ------------------------
10    1.  If a group that contained a recursive back reference also contained a
11        forward reference subroutine call followed by a non-forward-reference
12        subroutine call, for example /.((?2)(?R)\1)()/, pcre2_compile() failed to
13        compile correct code, leading to undefined behaviour or an internally
14        detected error. This bug was discovered by the LLVM fuzzer.
16  2.  Fixed a bug in the code for calculating the fixed length of lookbehind  2.  Quantification of certain items (e.g. atomic back references) could cause
17      assertions.      incorrect code to be compiled when recursive forward references were
18        involved. For example, in this pattern: /(?1)()((((((\1++))\x85)+)|))/.
19        This bug was discovered by the LLVM fuzzer.
21  3.  Removed the function pcre_info(), which has been obsolete and deprecated  3.  A repeated conditional group whose condition was a reference by name caused
22      since it was replaced by pcre_fullinfo() in February 2000.      a buffer overflow if there was more than one group with the given name.
23        This bug was discovered by the LLVM fuzzer.
25    4.  A recursive back reference by name within a group that had the same name as
26        another group caused a buffer overflow. For example:
27        /(?J)(?'d'(?'d'\g{d}))/. This bug was discovered by the LLVM fuzzer.
29    5.  A forward reference by name to a group whose number is the same as the
30        current group, for example in this pattern: /(?|(\k'Pm')|(?'Pm'))/, caused
31        a buffer overflow at compile time. This bug was discovered by the LLVM
32        fuzzer.
34    6.  A lookbehind assertion within a set of mutually recursive subpatterns could
35        provoke a buffer overflow. This bug was discovered by the LLVM fuzzer.
37    7.  Another buffer overflow bug involved duplicate named groups with a
38        reference between their definition, with a group that reset capture
39        numbers, for example: /(?J:(?|(?'R')(\k'R')|((?'R'))))/. This has been
40        fixed by always allowing for more memory, even if not needed. (A proper fix
41        is implemented in PCRE2, but it involves more refactoring.)
43    8.  There was no check for integer overflow in subroutine calls such as (?123).
45    9.  The table entry for \l in EBCDIC environments was incorrect, leading to its
46        being treated as a literal 'l' instead of causing an error.
48    10. There was a buffer overflow if pcre_exec() was called with an ovector of
49        size 1. This bug was found by american fuzzy lop.
51    11. If a non-capturing group containing a conditional group that could match
52        an empty string was repeated, it was not identified as matching an empty
53        string itself. For example: /^(?:(?(1)x|)+)+$()/.
55    12. In an EBCDIC environment, pcretest was mishandling the escape sequences
56        \a and \e in test subject lines.
58    13. In an EBCDIC environment, \a in a pattern was converted to the ASCII
59        instead of the EBCDIC value.
61    14. The handling of \c in an EBCDIC environment has been revised so that it is
62        now compatible with the specification in Perl's perlebcdic page.
64    15. The EBCDIC character 0x41 is a non-breaking space, equivalent to 0xa0 in
65        ASCII/Unicode. This has now been added to the list of characters that are
66        recognized as white space in EBCDIC.
68    16. When PCRE was compiled without UCP support, the use of \p and \P gave an
69        error (correctly) when used outside a class, but did not give an error
70        within a class.
72    17. \h within a class was incorrectly compiled in EBCDIC environments.
74    18. A pattern with an unmatched closing parenthesis that contained a backward
75        assertion which itself contained a forward reference caused buffer
76        overflow. And example pattern is: /(?=di(?<=(?1))|(?=(.))))/.
78    19. JIT should return with error when the compiled pattern requires more stack
79        space than the maximum.
81    20. A possessively repeated conditional group that could match an empty string,
82        for example, /(?(R))*+/, was incorrectly compiled.
84    21. Fix infinite recursion in the JIT compiler when certain patterns such as
85        /(?:|a|){100}x/ are analysed.
87    22. Some patterns with character classes involving [: and \\ were incorrectly
88        compiled and could cause reading from uninitialized memory or an incorrect
89        error diagnosis.
91    23. Pathological patterns containing many nested occurrences of [: caused
92        pcre_compile() to run for a very long time.
94    24. A conditional group with only one branch has an implicit empty alternative
95        branch and must therefore be treated as potentially matching an empty
96        string.
98    25. If (?R was followed by - or + incorrect behaviour happened instead of a
99        diagnostic.
101    26. Arrange to give up on finding the minimum matching length for overly
102        complex patterns.
104    27. Similar to (4) above: in a pattern with duplicated named groups and an
105        occurrence of (?| it is possible for an apparently non-recursive back
106        reference to become recursive if a later named group with the relevant
107        number is encountered. This could lead to a buffer overflow. Wen Guanxing
108        from Venustech ADLAB discovered this bug.
110    28. If pcregrep was given the -q option with -c or -l, or when handling a
111        binary file, it incorrectly wrote output to stdout.
113    29. The JIT compiler did not restore the control verb head in case of *THEN
114        control verbs. This issue was found by Karl Skomski with a custom LLVM fuzzer.
117    Version 8.37 28-April-2015
118    --------------------------
120    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
121        for those parentheses to be closed with whatever has been captured so far.
122        However, it was failing to mark any other groups between the hightest
123        capture so far and the currrent group as "unset". Thus, the ovector for
124        those groups contained whatever was previously there. An example is the
125        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
127    2.  If an assertion condition was quantified with a minimum of zero (an odd
128        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
130    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
131        unrecognized modifier, a crash could occur.
133    4.  An attempt to do global matching in pcretest with a zero-length ovector
134        caused a crash.
136    5.  Fixed a memory leak during matching that could occur for a subpattern
137        subroutine call (recursive or otherwise) if the number of captured groups
138        that had to be saved was greater than ten.
140    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
141        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
142        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
144    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
145        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
147    8. When a pattern is compiled, it remembers the highest back reference so that
148       when matching, if the ovector is too small, extra memory can be obtained to
149       use instead. A conditional subpattern whose condition is a check on a
150       capture having happened, such as, for example in the pattern
151       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
152       setting the highest backreference number. This mattered only if pcre_exec()
153       was called with an ovector that was too small to hold the capture, and there
154       was no other kind of back reference (a situation which is probably quite
155       rare). The effect of the bug was that the condition was always treated as
156       FALSE when the capture could not be consulted, leading to a incorrect
157       behaviour by pcre_exec(). This bug has been fixed.
159    9. A reference to a duplicated named group (either a back reference or a test
160       for being set in a conditional) that occurred in a part of the pattern where
161       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
162       to be incorrectly calculated, leading to overwriting.
164    10. A mutually recursive set of back references such as (\2)(\1) caused a
165        segfault at study time (while trying to find the minimum matching length).
166        The infinite loop is now broken (with the minimum length unset, that is,
167        zero).
169    11. If an assertion that was used as a condition was quantified with a minimum
170        of zero, matching went wrong. In particular, if the whole group had
171        unlimited repetition and could match an empty string, a segfault was
172        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
173        assertions to be quantified, but not if they are being used as conditions,
174        so the above pattern is faulted by Perl. PCRE has now been changed so that
175        it also rejects such patterns.
177    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
178        failed to allow the zero-repeat case if pcre2_exec() was called with an
179        ovector too small to capture the group.
181    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
182        Red Hat Product Security:
184        (a) A crash if /K and /F were both set with the option to save the compiled
185        pattern.
187        (b) Another crash if the option to print captured substrings in a callout
188        was combined with setting a null ovector, for example \O\C+ as a subject
189        string.
191    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
192        forward reference repeated a large (but limited) number of times within a
193        repeated outer group that has a zero minimum quantifier, caused incorrect
194        code to be compiled, leading to the error "internal error:
195        previously-checked referenced subpattern not found" when an incorrect
196        memory address was read. This bug was reported as "heap overflow",
197        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
198        CVE-2015-2325.
200    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
201        call within a group that also contained a recursive back reference caused
202        incorrect code to be compiled. This bug was reported as "heap overflow",
203        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
204        number CVE-2015-2326.
206    24. Computing the size of the JIT read-only data in advance has been a source
207        of various issues, and new ones are still appear unfortunately. To fix
208        existing and future issues, size computation is eliminated from the code,
209        and replaced by on-demand memory allocation.
211    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
212        adjacent to the end of the range, and the range contained characters with
213        more than one other case, caused incorrect behaviour when compiled in UTF
214        mode. In that example, the range a-j was left out of the class.
216    26. Fix JIT compilation of conditional blocks, which assertion
217        is converted to (*FAIL). E.g: /(?(?!))/.
219    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
220        discovered by the LLVM fuzzer.
222    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
223        when this assertion was used as a condition, for example (?(?!)a|b). In
224        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
225        error about an unsupported item.
227    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
228        possessification code could take exponential time to complete. A recursion
229        depth limit of 1000 has been imposed to limit the resources used by this
230        optimization.
232    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
233        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
234        because \S ensures they are all in the class. The code for doing this was
235        interacting badly with the code for computing the amount of space needed to
236        compile the pattern, leading to a buffer overflow. This bug was discovered
237        by the LLVM fuzzer.
239    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
240        other kinds of group caused stack overflow at compile time. This bug was
241        discovered by the LLVM fuzzer.
243    32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
244        between a subroutine call and its quantifier was incorrectly compiled,
245        leading to buffer overflow or other errors. This bug was discovered by the
246        LLVM fuzzer.
248    33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
249        assertion after (?(. The code was failing to check the character after
250        (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
251        was discovered by the LLVM fuzzer.
253    34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
254        a fixed maximum following a group that contains a subroutine reference was
255        incorrectly compiled and could trigger buffer overflow. This bug was
256        discovered by the LLVM fuzzer.
258    35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
259        caused a stack overflow instead of the diagnosis of a non-fixed length
260        lookbehind assertion. This bug was discovered by the LLVM fuzzer.
262    36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
263        (e.g. /(?<=\Ka)/) could make pcregrep loop.
265    37. There was a similar problem to 36 in pcretest for global matches.
267    38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
268        and a subsequent item in the pattern caused a non-match, backtracking over
269        the repeated \X did not stop, but carried on past the start of the subject,
270        causing reference to random memory and/or a segfault. There were also some
271        other cases where backtracking after \C could crash. This set of bugs was
272        discovered by the LLVM fuzzer.
274    39. The function for finding the minimum length of a matching string could take
275        a very long time if mutual recursion was present many times in a pattern,
276        for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
277        method has been implemented. This infelicity was discovered by the LLVM
278        fuzzer.
280    40. Static linking against the PCRE library using the pkg-config module was
281        failing on missing pthread symbols.
284    Version 8.36 26-September-2014
285    ------------------------------
287    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
288        -Wmissing-field-initializers and -Wunused-parameter.
290    2.  The tests for quantifiers being too big (greater than 65535) were being
291        applied after reading the number, and stupidly assuming that integer
292        overflow would give a negative number. The tests are now applied as the
293        numbers are read.
295    3.  Tidy code in pcre_exec.c where two branches that used to be different are
296        now the same.
298    4.  The JIT compiler did not generate match limit checks for certain
299        bracketed expressions with quantifiers. This may lead to exponential
300        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
301        issue should be resolved now.
303    5.  Fixed an issue, which occures when nested alternatives are optimized
304        with table jumps.
306    6.  Inserted two casts and changed some ints to size_t in the light of some
307        reported 64-bit compiler warnings (Bugzilla 1477).
309    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
310        an empty string, which sometimes were behaving incorrectly in the
311        interpreter (though correctly in the JIT matcher). This pcretest input is
312        an example:
314          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
317        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
318        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
319        for an empty string was breaking the inner loop and carrying on at a lower
320        level, when possessive repeated groups should always return to a higher
321        level as they have no backtrack points in them. The empty string test now
322        occurs at the outer level.
324    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
325        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
327    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
328        doesn't).
330    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
331        to hold a pattern to be incorrectly computed (too small) when there were
332        named back references to duplicated names. This could cause "internal
333        error: code overflow" or "double free or corruption" or other memory
334        handling errors.
336    11. When named subpatterns had the same prefixes, back references could be
337        confused. For example, in this pattern:
339          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
341        the reference to 'Name' was incorrectly treated as a reference to a
342        duplicate name.
344    12. A pattern such as /^s?c/mi8 where the optional character has more than
345        one "other case" was incorrectly compiled such that it would only try to
346        match starting at "c".
348    13. When a pattern starting with \s was studied, VT was not included in the
349        list of possible starting characters; this should have been part of the
350        8.34/18 patch.
352    14. If a character class started [\Qx]... where x is any character, the class
353        was incorrectly terminated at the ].
355    15. If a pattern that started with a caseless match for a character with more
356        than one "other case" was studied, PCRE did not set up the starting code
357        unit bit map for the list of possible characters. Now it does. This is an
358        optimization improvement, not a bug fix.
360    16. The Unicode data tables have been updated to Unicode 7.0.0.
362    17. Fixed a number of memory leaks in pcregrep.
364    18. Avoid a compiler warning (from some compilers) for a function call with
365        a cast that removes "const" from an lvalue by using an intermediate
366        variable (to which the compiler does not object).
368    19. Incorrect code was compiled if a group that contained an internal recursive
369        back reference was optional (had quantifier with a minimum of zero). This
370        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
371        caused segmentation faults because of stack overflows at compile time.
373    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
374        group that is quantified with an indefinite repeat, caused a compile-time
375        loop which used up all the system stack and provoked a segmentation fault.
376        This was not the same bug as 19 above.
378    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
379        Patch by Mike Frysinger.
382    Version 8.35 04-April-2014
383    --------------------------
385    1.  A new flag is set, when property checks are present in an XCLASS.
386        When this flag is not set, PCRE can perform certain optimizations
387        such as studying these XCLASS-es.
389    2.  The auto-possessification of character sets were improved: a normal
390        and an extended character set can be compared now. Furthermore
391        the JIT compiler optimizes more character set checks.
393    3.  Got rid of some compiler warnings for potentially uninitialized variables
394        that show up only when compiled with -O2.
396    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
397        of a match later then the end of the match. The pcretest program was not
398        handling the case sensibly - it was outputting from the start to the next
399        binary zero. It now reports this situation in a message, and outputs the
400        text from the end to the start.
402    5.  Fast forward search is improved in JIT. Instead of the first three
403        characters, any three characters with fixed position can be searched.
404        Search order: first, last, middle.
406    6.  Improve character range checks in JIT. Characters are read by an inprecise
407        function now, which returns with an unknown value if the character code is
408        above a certain threshold (e.g: 256). The only limitation is that the value
409        must be bigger than the threshold as well. This function is useful when
410        the characters above the threshold are handled in the same way.
412    7.  The macros whose names start with RAWUCHAR are placeholders for a future
413        mode in which only the bottom 21 bits of 32-bit data items are used. To
414        make this more memorable for those maintaining the code, the names have
415        been changed to start with UCHAR21, and an extensive comment has been added
416        to their definition.
418    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
419        to the export list in Makefile.am (they were accidentally omitted from the
420        8.34 tarball).
422    9.  The informational output from pcretest used the phrase "starting byte set"
423        which is inappropriate for the 16-bit and 32-bit libraries. As the output
424        for "first char" and "need char" really means "non-UTF-char", I've changed
425        "byte" to "char", and slightly reworded the output. The documentation about
426        these values has also been (I hope) clarified.
428    10. Another JIT related optimization: use table jumps for selecting the correct
429        backtracking path, when more than four alternatives are present inside a
430        bracket.
432    11. Empty match is not possible, when the minimum length is greater than zero,
433        and there is no \K in the pattern. JIT should avoid empty match checks in
434        such cases.
436    12. In a caseless character class with UCP support, when a character with more
437        than one alternative case was not the first character of a range, not all
438        the alternative cases were added to the class. For example, s and \x{17f}
439        are both alternative cases for S: the class [RST] was handled correctly,
440        but [R-T] was not.
442    13. The configure.ac file always checked for pthread support when JIT was
443        enabled. This is not used in Windows, so I have put this test inside a
444        check for the presence of windows.h (which was already tested for).
446    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
447        The algorithm provides a way to skip certain starting offsets, and usually
448        faster than linear prefix searches.
450    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
451        as for 'fr_FR' and 'french'. For some reason, however, it then used the
452        Windows-specific input and output files, which have 'french' screwed in.
453        So this could never have worked. One of the problems with locales is that
454        they aren't always the same. I have now updated RunTest so that it checks
455        the output of the locale test (test 3) against three different output
456        files, and it allows the test to pass if any one of them matches. With luck
457        this should make the test pass on some versions of Solaris where it was
458        failing. Because of the uncertainty, the script did not used to stop if
459        test 3 failed; it now does. If further versions of a French locale ever
460        come to light, they can now easily be added.
462    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
463        there was a message during ./configure, but it did not stop. This now
464        provokes an error. The invalid example in README has been corrected.
465        If a value less than the minimum is given, the minimum value has always
466        been used, but now a warning is given.
468    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
469        was a bug in the test system, which is now fixed. Also, the list of various
470        configurations that are tested for each release did not have one with both
471        16/32 bits and --enable-bar-anycrlf. It now does.
473    18. pcretest was missing "-C bsr" for displaying the \R default setting.
475    19. Little endian PowerPC systems are supported now by the JIT compiler.
477    20. The fast forward newline mechanism could enter to an infinite loop on
478        certain invalid UTF-8 input. Although we don't support these cases
479        this issue can be fixed by a performance optimization.
481    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
482        not take account if existing stack usage. There is now a new global
483        variable called pcre_stack_guard that can be set to point to an external
484        function to check stack availability. It is called at the start of
485        processing every parenthesized group.
487    22. A typo in the code meant that in ungreedy mode the max/min qualifier
488        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
489        not match "ab".
491    23. When UTF was disabled, the JIT program reported some incorrect compile
492        errors. These messages are silenced now.
494    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
495        compiler.
497    25. Change all the temporary files used in RunGrepTest to be different to those
498        used by RunTest so that the tests can be run simultaneously, for example by
499        "make -j check".
502    Version 8.34 15-December-2013
503    -----------------------------
505    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
506        executable memory. Patch inspired by Carsten Klein.
508    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
509        this macro is never tested and has no effect, because the work to support
510        coverage involves only compiling and linking options and special targets in
511        the Makefile. The comment in config.h implied that defining the macro would
512        enable coverage support, which is totally false. There was also support for
513        setting this macro in the CMake files (my fault, I just copied it from
514        configure). SUPPORT_GCOV has now been removed.
516    3.  Make a small performance improvement in strlen16() and strlen32() in
517        pcretest.
519    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
520        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
521        these cases). There was also one in pcretest.c.
523    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
525    6.  In UTF mode, the code for checking whether a group could match an empty
526        string (which is used for indefinitely repeated groups to allow for
527        breaking an infinite loop) was broken when the group contained a repeated
528        negated single-character class with a character that occupied more than one
529        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
530        UTF-8 mode). The effect was undefined: the group might or might not be
531        deemed as matching an empty string, or the program might have crashed.
533    7.  The code for checking whether a group could match an empty string was not
534        recognizing that \h, \H, \v, \V, and \R must match a character.
536    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
537        an empty string. If it can, pcretest shows this in its information output.
539    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
540        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
541        matched by pcre_exec() without using JIT:
543        (a) If the rest of the pattern did not match after a maximal run of
544            grapheme clusters, the code for backing up to try with fewer of them
545            did not always back up over a full grapheme when characters that do not
546            have the modifier quality were involved, e.g. Hangul syllables.
548        (b) If the match point in a subject started with modifier character, and
549            there was no match, the code could incorrectly back up beyond the match
550            point, and potentially beyond the first character in the subject,
551            leading to a segfault or an incorrect match result.
553    10. A conditional group with an assertion condition could lead to PCRE
554        recording an incorrect first data item for a match if no other first data
555        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
556        first data item, and therefore matched "ca" after "c" instead of at the
557        start.
559    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
560        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
562    12. The source of pcregrep now includes z/OS-specific code so that it can be
563        compiled for z/OS as part of the special z/OS distribution.
565    13. Added the -T and -TM options to pcretest.
567    14. The code in pcre_compile.c for creating the table of named capturing groups
568        has been refactored. Instead of creating the table dynamically during the
569        actual compiling pass, the information is remembered during the pre-compile
570        pass (on the stack unless there are more than 20 named groups, in which
571        case malloc() is used) and the whole table is created before the actual
572        compile happens. This has simplified the code (it is now nearly 150 lines
573        shorter) and prepared the way for better handling of references to groups
574        with duplicate names.
576    15. A back reference to a named subpattern when there is more than one of the
577        same name now checks them in the order in which they appear in the pattern.
578        The first one that is set is used for the reference. Previously only the
579        first one was inspected. This change makes PCRE more compatible with Perl.
581    16. Unicode character properties were updated from Unicode 6.3.0.
583    17. The compile-time code for auto-possessification has been refactored, based
584        on a patch by Zoltan Herczeg. It now happens after instead of during
585        compilation. The code is cleaner, and more cases are handled. The option
586        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
587        options in pcretest are provided to set it. It can also be set by
588        (*NO_AUTO_POSSESS) at the start of a pattern.
590    18. The character VT has been added to the default ("C" locale) set of
591        characters that match \s and are generally treated as white space,
592        following this same change in Perl 5.18. There is now no difference between
593        "Perl space" and "POSIX space". Whether VT is treated as white space in
594        other locales depends on the locale.
596    19. The code for checking named groups as conditions, either for being set or
597        for being recursed, has been refactored (this is related to 14 and 15
598        above). Processing unduplicated named groups should now be as fast at
599        numerical groups, and processing duplicated groups should be faster than
600        before.
602    20. Two patches to the CMake build system, by Alexander Barkov:
604          (1) Replace the "source" command by "." in CMakeLists.txt because
605              "source" is a bash-ism.
607          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
608              without these the CMake build does not work on Solaris.
610    21. Perl has changed its handling of \8 and \9. If there is no previously
611        encountered capturing group of those numbers, they are treated as the
612        literal characters 8 and 9 instead of a binary zero followed by the
613        literals. PCRE now does the same.
615    22. Following Perl, added \o{} to specify codepoints in octal, making it
616        possible to specify values greater than 0777 and also making them
617        unambiguous.
619    23. Perl now gives an error for missing closing braces after \x{... instead of
620        treating the string as literal. PCRE now does the same.
622    24. RunTest used to grumble if an inappropriate test was selected explicitly,
623        but just skip it when running all tests. This make it awkward to run ranges
624        of tests when one of them was inappropriate. Now it just skips any
625        inappropriate tests, as it always did when running all tests.
627    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
628        character types such as \d or \w, too many callouts were inserted, and the
629        data that they returned was rubbish.
631    26. In UCP mode, \s was not matching two of the characters that Perl matches,
632        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
633        were matched by \h. The code has now been refactored so that the lists of
634        the horizontal and vertical whitespace characters used for \h and \v (which
635        are defined only in one place) are now also used for \s.
637    27. Add JIT support for the 64 bit TileGX architecture.
638        Patch by Jiong Wang (Tilera Corporation).
640    28. Possessive quantifiers for classes (both explicit and automatically
641        generated) now use special opcodes instead of wrapping in ONCE brackets.
643    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
644        (because it's meaningless), this was not happening when PCRE_CASELESS was
645        set. Not wrong, but inefficient.
647    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
648        properties for \w, \d, etc) is present in a test regex. Otherwise if the
649        test contains no characters greater than 255, Perl doesn't realise it
650        should be using Unicode semantics.
652    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
653        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
654        does in Unicode mode.
656    32. Added the "forbid" facility to pcretest so that putting tests into the
657        wrong test files can sometimes be quickly detected.
659    33. There is now a limit (default 250) on the depth of nesting of parentheses.
660        This limit is imposed to control the amount of system stack used at compile
661        time. It can be changed at build time by --with-parens-nest-limit=xxx or
662        the equivalent in CMake.
664    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
665        errors. Perl warns for these when in warning mode, but PCRE has no facility
666        for giving warnings.
668    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
669        However, this was not working for (?!) because it is optimized to (*FAIL),
670        for which PCRE does not allow quantifiers. The optimization is now disabled
671        when a quantifier follows (?!). I can't see any use for this, but it makes
672        things uniform.
674    36. Perl no longer allows group names to start with digits, so I have made this
675        change also in PCRE. It simplifies the code a bit.
677    37. In extended mode, Perl ignores spaces before a + that indicates a
678        possessive quantifier. PCRE allowed a space before the quantifier, but not
679        before the possessive +. It now does.
681    38. The use of \K (reset reported match start) within a repeated possessive
682        group such as (a\Kb)*+ was not working.
684    40. Document that the same character tables must be used at compile time and
685        run time, and that the facility to pass tables to pcre_exec() and
686        pcre_dfa_exec() is for use only with saved/restored patterns.
688    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
689        features for Builds with MSVC:
691        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
692           builds). The .rc files can be used to set FileDescription and many other
693           attributes.
695        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
696           This allows higher-level build scripts which want .pdb files to avoid
697           hard-coding the exact files needed."
699    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
700        mean "start of word" and "end of word", respectively, as a transition aid.
702    43. A minimizing repeat of a class containing codepoints greater than 255 in
703        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
704        compiled to use the heap for recursion.
706    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
707        is configured.
710    Version 8.33 28-May-2013
711    ------------------------
713    1.  Added 'U' to some constants that are compared to unsigned integers, to
714        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
715        variables that are added to signed variables, to ensure the result is
716        signed and can be negated.
718    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
719        CMake config files.
721    3.  Revise the creation of config.h.generic so that all boolean macros are
722        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
723        overriding via -D on the command line possible.
725    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
726        to unsigned int is reported to make a quite noticeable speed difference in
727        a specific Windows environment. Testing on Linux did also appear to show
728        some benefit (and it is clearly not harmful). Also fixed the definition of
729        Xop which should be unsigned.
731    5.  Related to (4), changing the definition of the intermediate variable cc
732        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
733        improvements.
735    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
736        unnecessary spaces.
738    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
739        and later.
741    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
743    9.  Optimizing fast_forward_start_bits in JIT.
745    10. Adding support for callouts in JIT, and fixing some issues revealed
746        during this work. Namely:
748        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
750        (b) Minimum length was not checked before the matching is started.
752    11. The value of capture_last that is passed to callouts was incorrect in some
753        cases when there was a capture on one path that was subsequently abandoned
754        after a backtrack. Also, the capture_last value is now reset after a
755        recursion, since all captures are also reset in this case.
757    12. The interpreter no longer returns the "too many substrings" error in the
758        case when an overflowing capture is in a branch that is subsequently
759        abandoned after a backtrack.
761    13. In the pathological case when an offset vector of size 2 is used, pcretest
762        now prints out the matched string after a yield of 0 or 1.
764    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
765        Only supported by the JIT compiler at the moment.
767    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
769    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
770        offset of the starting point of the matching process, provided the offsets
771        vector is large enough.
773    17. The \A escape now records a lookbehind value of 1, though its execution
774        does not actually inspect the previous character. This is to ensure that,
775        in partial multi-segment matching, at least one character from the old
776        segment is retained when a new segment is processed. Otherwise, if there
777        are no lookbehinds in the pattern, \A might match incorrectly at the start
778        of a new segment.
780    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
782    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
783        gives some modest performance improvement in 8-bit mode.
785    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
786        be expressed in certain programming languages using Universal Character
787        Names.
789    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
790        which points out that "non characters" are not "characters that may not
791        appear in Unicode strings" but rather "characters that are reserved for
792        internal use and have only local meaning".
794    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
795        there was a conditional group that depended on an assertion, if the
796        assertion was false, the callout that immediately followed the alternation
797        in the condition was skipped when pcre_exec() was used for matching.
799    23. Allow an explicit callout to be inserted before an assertion that is the
800        condition for a conditional group, for compatibility with automatic
801        callouts, which always insert a callout at this point.
803    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
804        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
806    25. (*PRUNE) is now supported by the JIT compiler.
808    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
810    27. Fix the case where there are two or more SKIPs with arguments that may be
811        ignored.
813    28. (*SKIP) is now supported by the JIT compiler.
815    29. (*THEN) is now supported by the JIT compiler.
817    30. Update RunTest with additional test selector options.
819    31. The way PCRE handles backtracking verbs has been changed in two ways.
821        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
822        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
823        backtracking. In some cases this makes it more Perl-compatible, but Perl's
824        rather obscure rules do not always do the same thing.
826        (2) Previously, backtracking verbs were confined within assertions. This is
827        no longer the case for positive assertions, except for (*ACCEPT). Again,
828        this sometimes improves Perl compatibility, and sometimes does not.
830    32. A number of tests that were in test 2 because Perl did things differently
831        have been moved to test 1, because either Perl or PCRE has changed, and
832        these tests are now compatible.
834    32. Backtracking control verbs are now handled in the same way in JIT and
835        interpreter.
837    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
838        contained a forward subroutine reference caused a compile error.
840    34. Auto-detect and optimize limited repetitions in JIT.
842    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
843        blocking (*UTF) etc.
845    36. In the interpreter, maximizing pattern repetitions for characters and
846        character types now use tail recursion, which reduces stack usage.
848    37. The value of the max lookbehind was not correctly preserved if a compiled
849        and saved regex was reloaded on a host of different endianness.
851    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
852        of the compiled pattern block, expand the flags field from 16 to 32 bits
853        because it was almost full.
855    39. Try madvise first before posix_madvise.
857    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
858        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
859        original change locked out all matches of empty strings. This has been
860        changed so that one match of an empty string per line is recognized.
861        Subsequent searches on the same line (for colouring or for --only-matching,
862        for example) do not recognize empty strings.
864    41. Applied a user patch to fix a number of spelling mistakes in comments.
866    42. Data lines longer than 65536 caused pcretest to crash.
868    43. Clarified the data type for length and startoffset arguments for pcre_exec
869        and pcre_dfa_exec in the function-specific man pages, where they were
870        explicitly stated to be in bytes, never having been updated. I also added
871        some clarification to the pcreapi man page.
873    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
874        a segmentation fault.
877    Version 8.32 30-November-2012
878    -----------------------------
880    1.  Improved JIT compiler optimizations for first character search and single
881        character iterators.
883    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
884        Patch by Daniel Richard G.
886    3.  Single character iterator optimizations in the JIT compiler.
888    4.  Improved JIT compiler optimizations for character ranges.
890    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
891        Reported by Giuseppe D'Angelo.
893    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
894        of a line, was being set incorrectly in cases where .* appeared inside
895        atomic brackets at the start of a pattern, or where there was a subsequent
896        *PRUNE or *SKIP.
898    7.  Improved instruction cache flush for POWER/PowerPC.
899        Patch by Daniel Richard G.
901    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
902        grep:
904        (a) There is now no limit to the number of patterns to be matched.
906        (b) An error is given if a pattern is too long.
908        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
909            are now supported.
911        (d) --exclude-from and --include-from (multiple use) have been added.
913        (e) Exclusions and inclusions now apply to all files and directories, not
914            just to those obtained from scanning a directory recursively.
916        (f) Multiple uses of -f and --file-list are now supported.
918        (g) In a Windows environment, the default for -d has been changed from
919            "read" (the GNU grep default) to "skip", because otherwise the presence
920            of a directory in the file list provokes an error.
922        (h) The documentation has been revised and clarified in places.
924    9.  Improve the matching speed of capturing brackets.
926    10. Changed the meaning of \X so that it now matches a Unicode extended
927        grapheme cluster.
929    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
930        out POSIX threads when JIT support is configured.
932    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
934    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
935        structure could go wrong in environments where size_t is not the same size
936        as int.
938    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
939        set.
941    15. The EBCDIC support had decayed; later updates to the code had included
942        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
943        general tidy up of EBCDIC-related issues, and the documentation was also
944        not quite right. There is now a test that can be run on ASCII systems to
945        check some of the EBCDIC-related things (but is it not a full test).
947    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
948        in a small tidy to the code.
950    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
952    18. If the --only-matching (-o) option in pcregrep is specified multiple
953        times, each one causes appropriate output. For example, -o1 -o2 outputs the
954        substrings matched by the 1st and 2nd capturing parentheses. A separating
955        string can be specified by --om-separator (default empty).
957    19. Improving the first n character searches.
959    20. Turn case lists for horizontal and vertical white space into macros so that
960        they are defined only once.
962    21. This set of changes together give more compatible Unicode case-folding
963        behaviour for characters that have more than one other case when UCP
964        support is available.
966        (a) The Unicode property table now has offsets into a new table of sets of
967            three or more characters that are case-equivalent. The MultiStage2.py
968            script that generates these tables (the pcre_ucd.c file) now scans
969            CaseFolding.txt instead of UnicodeData.txt for character case
970            information.
972        (b) The code for adding characters or ranges of characters to a character
973            class has been abstracted into a generalized function that also handles
974            case-independence. In UTF-mode with UCP support, this uses the new data
975            to handle characters with more than one other case.
977        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
978            whose other case is greater than 256 are now correctly matched
979            caselessly. Previously, the high codepoint matched the low one, but not
980            vice versa.
982        (d) The processing of \h, \H, \v, and \ in character classes now makes use
983            of the new class addition function, using character lists defined as
984            macros alongside the case definitions of 20 above.
986        (e) Caseless back references now work with characters that have more than
987            one other case.
989        (f) General caseless matching of characters with more than one other case
990            is supported.
992    22. Unicode character properties were updated from Unicode 6.2.0
994    23. Improved CMake support under Windows. Patch by Daniel Richard G.
996    24. Add support for 32-bit character strings, and UTF-32
998    25. Major JIT compiler update (code refactoring and bugfixing).
999        Experimental Sparc 32 support is added.
1001    26. Applied a modified version of Daniel Richard G's patch to create
1002        pcre.h.generic and config.h.generic by "make" instead of in the
1003        PrepareRelease script.
1005    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
1006        pcre_compile.c when checking for a zero character.
1008    28. Introducing a native interface for JIT. Through this interface, the compiled
1009        machine code can be directly executed. The purpose of this interface is to
1010        provide fast pattern matching, so several sanity checks are not performed.
1011        However, feature tests are still performed. The new interface provides
1012        1.4x speedup compared to the old one.
1014    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
1015        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
1016        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
1018    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
1019        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
1020        the "old" RFC 2279). Instead, it ended up passing a negative length to
1021        pcre_exec().
1023    31. Add support for GCC's visibility feature to hide internal functions.
1025    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
1026        "unknown -C option" after outputting 0 or 1.
1028    33. There is now support for generating a code coverage report for the test
1029        suite in environments where gcc is the compiler and lcov is installed. This
1030        is mainly for the benefit of the developers.
1032    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
1033        unaddressable using valgrind annotations, allowing valgrind to detect
1034        invalid memory accesses. This is mainly for the benefit of the developers.
1036    25. (*UTF) can now be used to start a pattern in any of the three libraries.
1038    26. Give configure error if --enable-cpp but no C++ compiler found.
1041    Version 8.31 06-July-2012
1042    -------------------------
1044    1.  Fixing a wrong JIT test case and some compiler warnings.
1046    2.  Removed a bashism from the RunTest script.
1048    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
1049        to unsigned type, result still unsigned" that was given by an MS compiler
1050        on encountering the code "-sizeof(xxx)".
1052    4.  Partial matching support is added to the JIT compiler.
1054    5.  Fixed several bugs concerned with partial matching of items that consist
1055        of more than one character:
1057        (a) /^(..)\1/ did not partially match "aba" because checking references was
1058            done on an "all or nothing" basis. This also applied to repeated
1059            references.
1061        (b) \R did not give a hard partial match if \r was found at the end of the
1062            subject.
1064        (c) \X did not give a hard partial match after matching one or more
1065            characters at the end of the subject.
1067        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
1068            a partial match for the string "\r".
1070        (e) When newline was set to CRLF, the metacharacter "." did not recognize
1071            a partial match for a CR character at the end of the subject string.
1073    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
1074        running pcretest, the text "(JIT)" added to the output whenever JIT is
1075        actually used to run the match.
1077    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
1078        or /S+[+] with a digit between 1 and 7.
1080    8.  OP_NOT now supports any UTF character not just single-byte ones.
1082    9.  (*MARK) control verb is now supported by the JIT compiler.
1084    10. The command "./RunTest list" lists the available tests without actually
1085        running any of them. (Because I keep forgetting what they all are.)
1089    12. Applied a (slightly modified) user-supplied patch that improves performance
1090        when the heap is used for recursion (compiled with --disable-stack-for-
1091        recursion). Instead of malloc and free for each heap frame each time a
1092        logical recursion happens, frames are retained on a chain and re-used where
1093        possible. This sometimes gives as much as 30% improvement.
1095    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
1096        call.
1098    14. As documented, (*COMMIT) is now confined to within a positive assertion.
1100    15. It is now possible to link pcretest with libedit as an alternative to
1101        libreadline.
1103    16. (*COMMIT) control verb is now supported by the JIT compiler.
1105    17. The Unicode data tables have been updated to Unicode 6.1.0.
1107    18. Added --file-list option to pcregrep.
1109    19. Added binary file support to pcregrep, including the -a, --binary-files,
1110        -I, and --text options.
1112    20. The madvise function is renamed for posix_madvise for QNX compatibility
1113        reasons. Fixed by Giuseppe D'Angelo.
1115    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
1117    22. Changed the option for creating symbolic links for 16-bit man pages from
1118        -s to -sf so that re-installing does not cause issues.
1120    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
1122    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
1123        matches in certain environments (the workspace was not being correctly
1124        retained). Also added to pcre_dfa_exec() a simple plausibility check on
1125        some of the workspace data at the beginning of a restart.
1127    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
1128        was not doing so when it should - probably a typo introduced by SVN 528
1129        (change 8.10/14).
1131    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
1132        \w+ when the character tables indicated that \x{c4} was a word character.
1133        There were several related cases, all because the tests for doing a table
1134        lookup were testing for characters less than 127 instead of 255.
1136    27. If a pattern contains capturing parentheses that are not used in a match,
1137        their slots in the ovector are set to -1. For those that are higher than
1138        any matched groups, this happens at the end of processing. In the case when
1139        there were back references that the ovector was too small to contain
1140        (causing temporary malloc'd memory to be used during matching), and the
1141        highest capturing number was not used, memory off the end of the ovector
1142        was incorrectly being set to -1. (It was using the size of the temporary
1143        memory instead of the true size.)
1145    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
1146        ovector size, it uses memory at the end of the block that it has got.
1148    29. Check for an overlong MARK name and give an error at compile time. The
1149        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
1151    30. JIT compiler update.
1153    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
1154        Rill for the patch.
1156    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
1158    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
1160    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
1161        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
1162        was enabled.
1164    35. Improve JIT code generation for greedy plus quantifier.
1166    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
1167        1 to "aa" instead of to an empty string. The bug affected repeated groups
1168        that could potentially match an empty string.
1170    37. Optimizing single character iterators in JIT.
1172    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
1173        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
1174        codepoints that are too big for the mode are faulted, and in a UTF mode,
1175        disallowed codepoints are also faulted.
1177    39. If PCRE was compiled with UTF support, in three places in the DFA
1178        matcher there was code that should only have been obeyed in UTF mode, but
1179        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
1180        processing when bytes with values greater than 127 were present. In 16-bit
1181        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
1182        both cases the values are those that cannot be the first data item in a UTF
1183        character. The three items that might have provoked this were recursions,
1184        possessively repeated groups, and atomic groups.
1186    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
1187        and pcregrep, because some OS require shared objects to be explicitly
1188        passed to ld, causing the link step to fail if they are not.
1190    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
1191        mode, patterns that started with \h* or \R* might be incorrectly matched.
1194    Version 8.30 04-February-2012
1195    -----------------------------
1197    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
1198        name is defined in ctype.h.
1200    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
1201        only in quite long subpatterns.
1203    3.  Removed the function pcre_info(), which has been obsolete and deprecated
1204        since it was replaced by pcre_fullinfo() in February 2000.
1206  4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not  4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
1207      match a (*MARK), and the match failed at the start of the subject, a      match a (*MARK), and the match failed at the start of the subject, a
1208      reference to memory before the start of the subject could occur. This bug      reference to memory before the start of the subject could occur. This bug
1209      was introduced by fix 17 of release 8.21.      was introduced by fix 17 of release 8.21.
1211  5.  A reference to an unset group with zero minimum repetition was giving  5.  A reference to an unset group with zero minimum repetition was giving
1212      totally wrong answers (in non-JavaScript-compatibility mode). For example,      totally wrong answers (in non-JavaScript-compatibility mode). For example,
1213      /(another)?(\1?)test/ matched against "hello world test". This bug was      /(another)?(\1?)test/ matched against "hello world test". This bug was
1214      introduced in release 8.13.      introduced in release 8.13.
1216  6.  Add support for 16-bit character strings (a large amount of work involving  6.  Add support for 16-bit character strings (a large amount of work involving
1217      many changes and refactorings).      many changes and refactorings).
1219    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
1220        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
1221        from a file.
1223    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
1224        rounding is not applied in this particular case).
1226    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
1227        if they appear, or are escaped, in patterns.
1229    10. Get rid of a number of -Wunused-but-set-variable warnings.
1231    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
1232        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
1233        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
1234        also returns the mark "x". This bug applied to capturing parentheses,
1235        non-capturing parentheses, and atomic parentheses. It also applied to some
1236        assertions.
1238    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
1239        information out of configure.ac instead of relying on pcre.h.generic, which
1240        is not stored in the repository.
1242    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
1243        -lreadline.
1245    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
1247    15. Applied Graycode's patch to put the top-level frame on the stack rather
1248        than the heap when not using the stack for recursion. This gives a
1249        performance improvement in many cases when recursion is not deep.
1251    16. Experimental code added to "pcretest -C" to output the stack frame size.
1254  Version 8.21 12-Dec-2011  Version 8.21 12-Dec-2011
1255  ------------------------  ------------------------
# Line 1157  Version 7.9 11-Apr-09 Line 2381  Version 7.9 11-Apr-09
2381  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
2382      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
2383      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2384      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2385        8.33.]
2387  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
2388      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1400  Version 7.7 07-May-08 Line 2625  Version 7.7 07-May-08
2625      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2626      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2627      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2628      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2629      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2630      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.836  
changed lines
  Added in v.1587

  ViewVC Help
Powered by ViewVC 1.1.5