ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 934 by ph10, Sat Feb 25 12:30:36 2012 UTC revision 1606 by ph10, Tue Nov 17 18:00:03 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.31  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    Version 8.38 27-October-2015
8    ----------------------------
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.  Quantification of certain items (e.g. atomic back references) could cause
17        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.  A repeated conditional group whose condition was a reference by name caused
22        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
115        fuzzer.
117    30. Error messages for syntax errors following \g and \k were giving inaccurate
118        offsets in the pattern.
120    31. Added a check for integer overflow in conditions (?(<digits>) and
121        (?(R<digits>). This omission was discovered by Karl Skomski with the LLVM
122        fuzzer.
124    32. Handling recursive references such as (?2) when the reference is to a group
125        later in the pattern uses code that is very hacked about and error-prone.
126        It has been re-written for PCRE2. Here in PCRE1, a check has been added to
127        give an internal error if it is obvious that compiling has gone wrong.
129    33. The JIT compiler should not check repeats after a {0,1} repeat byte code.
130        This issue was found by Karl Skomski with a custom LLVM fuzzer.
132    34. The JIT compiler should restore the control chain for empty possessive
133        repeats. This issue was found by Karl Skomski with a custom LLVM fuzzer.
135    35. Match limit check added to JIT recursion. This issue was found by Karl
136        Skomski with a custom LLVM fuzzer.
138    36. Yet another case similar to 27 above has been circumvented by an
139        unconditional allocation of extra memory. This issue is fixed "properly" in
140        PCRE2 by refactoring the way references are handled. Wen Guanxing
141        from Venustech ADLAB discovered this bug.
143    37. Fix two assertion fails in JIT. These issues were found by Karl Skomski
144        with a custom LLVM fuzzer.
146    38. Fixed a corner case of range optimization in JIT.
148    39. An incorrect error "overran compiling workspace" was given if there were
149        exactly enough group forward references such that the last one extended
150        into the workspace safety margin. The next one would have expanded the
151        workspace. The test for overflow was not including the safety margin.
153    40. A match limit issue is fixed in JIT which was found by Karl Skomski
154        with a custom LLVM fuzzer.
156    41. Remove the use of /dev/null in testdata/testinput2, because it doesn't
157        work under Windows. (Why has it taken so long for anyone to notice?)
159    42. In a character class such as [\W\p{Any}] where both a negative-type escape
160        ("not a word character") and a property escape were present, the property
161        escape was being ignored.
163    43. Fix crash caused by very long (*MARK) or (*THEN) names.
165    44. A sequence such as [[:punct:]b] that is, a POSIX character class followed
166        by a single ASCII character in a class item, was incorrectly compiled in
167        UCP mode. The POSIX class got lost, but only if the single character
168        followed it.
170    45. [:punct:] in UCP mode was matching some characters in the range 128-255
171        that should not have been matched.
174    Version 8.37 28-April-2015
175    --------------------------
177    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
178        for those parentheses to be closed with whatever has been captured so far.
179        However, it was failing to mark any other groups between the hightest
180        capture so far and the currrent group as "unset". Thus, the ovector for
181        those groups contained whatever was previously there. An example is the
182        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
184    2.  If an assertion condition was quantified with a minimum of zero (an odd
185        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
187    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
188        unrecognized modifier, a crash could occur.
190    4.  An attempt to do global matching in pcretest with a zero-length ovector
191        caused a crash.
193    5.  Fixed a memory leak during matching that could occur for a subpattern
194        subroutine call (recursive or otherwise) if the number of captured groups
195        that had to be saved was greater than ten.
197    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
198        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
199        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
201    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
202        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
204    8. When a pattern is compiled, it remembers the highest back reference so that
205       when matching, if the ovector is too small, extra memory can be obtained to
206       use instead. A conditional subpattern whose condition is a check on a
207       capture having happened, such as, for example in the pattern
208       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
209       setting the highest backreference number. This mattered only if pcre_exec()
210       was called with an ovector that was too small to hold the capture, and there
211       was no other kind of back reference (a situation which is probably quite
212       rare). The effect of the bug was that the condition was always treated as
213       FALSE when the capture could not be consulted, leading to a incorrect
214       behaviour by pcre_exec(). This bug has been fixed.
216    9. A reference to a duplicated named group (either a back reference or a test
217       for being set in a conditional) that occurred in a part of the pattern where
218       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
219       to be incorrectly calculated, leading to overwriting.
221    10. A mutually recursive set of back references such as (\2)(\1) caused a
222        segfault at study time (while trying to find the minimum matching length).
223        The infinite loop is now broken (with the minimum length unset, that is,
224        zero).
226    11. If an assertion that was used as a condition was quantified with a minimum
227        of zero, matching went wrong. In particular, if the whole group had
228        unlimited repetition and could match an empty string, a segfault was
229        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
230        assertions to be quantified, but not if they are being used as conditions,
231        so the above pattern is faulted by Perl. PCRE has now been changed so that
232        it also rejects such patterns.
234    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
235        failed to allow the zero-repeat case if pcre2_exec() was called with an
236        ovector too small to capture the group.
238    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
239        Red Hat Product Security:
241        (a) A crash if /K and /F were both set with the option to save the compiled
242        pattern.
244        (b) Another crash if the option to print captured substrings in a callout
245        was combined with setting a null ovector, for example \O\C+ as a subject
246        string.
248    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
249        forward reference repeated a large (but limited) number of times within a
250        repeated outer group that has a zero minimum quantifier, caused incorrect
251        code to be compiled, leading to the error "internal error:
252        previously-checked referenced subpattern not found" when an incorrect
253        memory address was read. This bug was reported as "heap overflow",
254        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
255        CVE-2015-2325.
257    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
258        call within a group that also contained a recursive back reference caused
259        incorrect code to be compiled. This bug was reported as "heap overflow",
260        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
261        number CVE-2015-2326.
263    24. Computing the size of the JIT read-only data in advance has been a source
264        of various issues, and new ones are still appear unfortunately. To fix
265        existing and future issues, size computation is eliminated from the code,
266        and replaced by on-demand memory allocation.
268    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
269        adjacent to the end of the range, and the range contained characters with
270        more than one other case, caused incorrect behaviour when compiled in UTF
271        mode. In that example, the range a-j was left out of the class.
273    26. Fix JIT compilation of conditional blocks, which assertion
274        is converted to (*FAIL). E.g: /(?(?!))/.
276    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
277        discovered by the LLVM fuzzer.
279    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
280        when this assertion was used as a condition, for example (?(?!)a|b). In
281        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
282        error about an unsupported item.
284    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
285        possessification code could take exponential time to complete. A recursion
286        depth limit of 1000 has been imposed to limit the resources used by this
287        optimization.
289    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
290        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
291        because \S ensures they are all in the class. The code for doing this was
292        interacting badly with the code for computing the amount of space needed to
293        compile the pattern, leading to a buffer overflow. This bug was discovered
294        by the LLVM fuzzer.
296    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
297        other kinds of group caused stack overflow at compile time. This bug was
298        discovered by the LLVM fuzzer.
300    32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
301        between a subroutine call and its quantifier was incorrectly compiled,
302        leading to buffer overflow or other errors. This bug was discovered by the
303        LLVM fuzzer.
305    33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
306        assertion after (?(. The code was failing to check the character after
307        (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
308        was discovered by the LLVM fuzzer.
310    34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
311        a fixed maximum following a group that contains a subroutine reference was
312        incorrectly compiled and could trigger buffer overflow. This bug was
313        discovered by the LLVM fuzzer.
315    35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
316        caused a stack overflow instead of the diagnosis of a non-fixed length
317        lookbehind assertion. This bug was discovered by the LLVM fuzzer.
319    36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
320        (e.g. /(?<=\Ka)/) could make pcregrep loop.
322    37. There was a similar problem to 36 in pcretest for global matches.
324    38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
325        and a subsequent item in the pattern caused a non-match, backtracking over
326        the repeated \X did not stop, but carried on past the start of the subject,
327        causing reference to random memory and/or a segfault. There were also some
328        other cases where backtracking after \C could crash. This set of bugs was
329        discovered by the LLVM fuzzer.
331    39. The function for finding the minimum length of a matching string could take
332        a very long time if mutual recursion was present many times in a pattern,
333        for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
334        method has been implemented. This infelicity was discovered by the LLVM
335        fuzzer.
337    40. Static linking against the PCRE library using the pkg-config module was
338        failing on missing pthread symbols.
341    Version 8.36 26-September-2014
342    ------------------------------
344    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
345        -Wmissing-field-initializers and -Wunused-parameter.
347    2.  The tests for quantifiers being too big (greater than 65535) were being
348        applied after reading the number, and stupidly assuming that integer
349        overflow would give a negative number. The tests are now applied as the
350        numbers are read.
352    3.  Tidy code in pcre_exec.c where two branches that used to be different are
353        now the same.
355    4.  The JIT compiler did not generate match limit checks for certain
356        bracketed expressions with quantifiers. This may lead to exponential
357        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
358        issue should be resolved now.
360    5.  Fixed an issue, which occures when nested alternatives are optimized
361        with table jumps.
363    6.  Inserted two casts and changed some ints to size_t in the light of some
364        reported 64-bit compiler warnings (Bugzilla 1477).
366    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
367        an empty string, which sometimes were behaving incorrectly in the
368        interpreter (though correctly in the JIT matcher). This pcretest input is
369        an example:
371          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
374        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
375        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
376        for an empty string was breaking the inner loop and carrying on at a lower
377        level, when possessive repeated groups should always return to a higher
378        level as they have no backtrack points in them. The empty string test now
379        occurs at the outer level.
381    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
382        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
384    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
385        doesn't).
387    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
388        to hold a pattern to be incorrectly computed (too small) when there were
389        named back references to duplicated names. This could cause "internal
390        error: code overflow" or "double free or corruption" or other memory
391        handling errors.
393    11. When named subpatterns had the same prefixes, back references could be
394        confused. For example, in this pattern:
396          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
398        the reference to 'Name' was incorrectly treated as a reference to a
399        duplicate name.
401    12. A pattern such as /^s?c/mi8 where the optional character has more than
402        one "other case" was incorrectly compiled such that it would only try to
403        match starting at "c".
405    13. When a pattern starting with \s was studied, VT was not included in the
406        list of possible starting characters; this should have been part of the
407        8.34/18 patch.
409    14. If a character class started [\Qx]... where x is any character, the class
410        was incorrectly terminated at the ].
412    15. If a pattern that started with a caseless match for a character with more
413        than one "other case" was studied, PCRE did not set up the starting code
414        unit bit map for the list of possible characters. Now it does. This is an
415        optimization improvement, not a bug fix.
417    16. The Unicode data tables have been updated to Unicode 7.0.0.
419    17. Fixed a number of memory leaks in pcregrep.
421    18. Avoid a compiler warning (from some compilers) for a function call with
422        a cast that removes "const" from an lvalue by using an intermediate
423        variable (to which the compiler does not object).
425    19. Incorrect code was compiled if a group that contained an internal recursive
426        back reference was optional (had quantifier with a minimum of zero). This
427        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
428        caused segmentation faults because of stack overflows at compile time.
430    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
431        group that is quantified with an indefinite repeat, caused a compile-time
432        loop which used up all the system stack and provoked a segmentation fault.
433        This was not the same bug as 19 above.
435    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
436        Patch by Mike Frysinger.
439    Version 8.35 04-April-2014
440    --------------------------
442    1.  A new flag is set, when property checks are present in an XCLASS.
443        When this flag is not set, PCRE can perform certain optimizations
444        such as studying these XCLASS-es.
446    2.  The auto-possessification of character sets were improved: a normal
447        and an extended character set can be compared now. Furthermore
448        the JIT compiler optimizes more character set checks.
450    3.  Got rid of some compiler warnings for potentially uninitialized variables
451        that show up only when compiled with -O2.
453    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
454        of a match later then the end of the match. The pcretest program was not
455        handling the case sensibly - it was outputting from the start to the next
456        binary zero. It now reports this situation in a message, and outputs the
457        text from the end to the start.
459    5.  Fast forward search is improved in JIT. Instead of the first three
460        characters, any three characters with fixed position can be searched.
461        Search order: first, last, middle.
463    6.  Improve character range checks in JIT. Characters are read by an inprecise
464        function now, which returns with an unknown value if the character code is
465        above a certain threshold (e.g: 256). The only limitation is that the value
466        must be bigger than the threshold as well. This function is useful when
467        the characters above the threshold are handled in the same way.
469    7.  The macros whose names start with RAWUCHAR are placeholders for a future
470        mode in which only the bottom 21 bits of 32-bit data items are used. To
471        make this more memorable for those maintaining the code, the names have
472        been changed to start with UCHAR21, and an extensive comment has been added
473        to their definition.
475    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
476        to the export list in Makefile.am (they were accidentally omitted from the
477        8.34 tarball).
479    9.  The informational output from pcretest used the phrase "starting byte set"
480        which is inappropriate for the 16-bit and 32-bit libraries. As the output
481        for "first char" and "need char" really means "non-UTF-char", I've changed
482        "byte" to "char", and slightly reworded the output. The documentation about
483        these values has also been (I hope) clarified.
485    10. Another JIT related optimization: use table jumps for selecting the correct
486        backtracking path, when more than four alternatives are present inside a
487        bracket.
489    11. Empty match is not possible, when the minimum length is greater than zero,
490        and there is no \K in the pattern. JIT should avoid empty match checks in
491        such cases.
493    12. In a caseless character class with UCP support, when a character with more
494        than one alternative case was not the first character of a range, not all
495        the alternative cases were added to the class. For example, s and \x{17f}
496        are both alternative cases for S: the class [RST] was handled correctly,
497        but [R-T] was not.
499    13. The configure.ac file always checked for pthread support when JIT was
500        enabled. This is not used in Windows, so I have put this test inside a
501        check for the presence of windows.h (which was already tested for).
503    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
504        The algorithm provides a way to skip certain starting offsets, and usually
505        faster than linear prefix searches.
507    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
508        as for 'fr_FR' and 'french'. For some reason, however, it then used the
509        Windows-specific input and output files, which have 'french' screwed in.
510        So this could never have worked. One of the problems with locales is that
511        they aren't always the same. I have now updated RunTest so that it checks
512        the output of the locale test (test 3) against three different output
513        files, and it allows the test to pass if any one of them matches. With luck
514        this should make the test pass on some versions of Solaris where it was
515        failing. Because of the uncertainty, the script did not used to stop if
516        test 3 failed; it now does. If further versions of a French locale ever
517        come to light, they can now easily be added.
519    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
520        there was a message during ./configure, but it did not stop. This now
521        provokes an error. The invalid example in README has been corrected.
522        If a value less than the minimum is given, the minimum value has always
523        been used, but now a warning is given.
525    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
526        was a bug in the test system, which is now fixed. Also, the list of various
527        configurations that are tested for each release did not have one with both
528        16/32 bits and --enable-bar-anycrlf. It now does.
530    18. pcretest was missing "-C bsr" for displaying the \R default setting.
532    19. Little endian PowerPC systems are supported now by the JIT compiler.
534    20. The fast forward newline mechanism could enter to an infinite loop on
535        certain invalid UTF-8 input. Although we don't support these cases
536        this issue can be fixed by a performance optimization.
538    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
539        not take account if existing stack usage. There is now a new global
540        variable called pcre_stack_guard that can be set to point to an external
541        function to check stack availability. It is called at the start of
542        processing every parenthesized group.
544    22. A typo in the code meant that in ungreedy mode the max/min qualifier
545        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
546        not match "ab".
548    23. When UTF was disabled, the JIT program reported some incorrect compile
549        errors. These messages are silenced now.
551    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
552        compiler.
554    25. Change all the temporary files used in RunGrepTest to be different to those
555        used by RunTest so that the tests can be run simultaneously, for example by
556        "make -j check".
559    Version 8.34 15-December-2013
560  -----------------------------  -----------------------------
562    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
563        executable memory. Patch inspired by Carsten Klein.
565    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
566        this macro is never tested and has no effect, because the work to support
567        coverage involves only compiling and linking options and special targets in
568        the Makefile. The comment in config.h implied that defining the macro would
569        enable coverage support, which is totally false. There was also support for
570        setting this macro in the CMake files (my fault, I just copied it from
571        configure). SUPPORT_GCOV has now been removed.
573    3.  Make a small performance improvement in strlen16() and strlen32() in
574        pcretest.
576    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
577        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
578        these cases). There was also one in pcretest.c.
580    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
582    6.  In UTF mode, the code for checking whether a group could match an empty
583        string (which is used for indefinitely repeated groups to allow for
584        breaking an infinite loop) was broken when the group contained a repeated
585        negated single-character class with a character that occupied more than one
586        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
587        UTF-8 mode). The effect was undefined: the group might or might not be
588        deemed as matching an empty string, or the program might have crashed.
590    7.  The code for checking whether a group could match an empty string was not
591        recognizing that \h, \H, \v, \V, and \R must match a character.
593    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
594        an empty string. If it can, pcretest shows this in its information output.
596    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
597        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
598        matched by pcre_exec() without using JIT:
600        (a) If the rest of the pattern did not match after a maximal run of
601            grapheme clusters, the code for backing up to try with fewer of them
602            did not always back up over a full grapheme when characters that do not
603            have the modifier quality were involved, e.g. Hangul syllables.
605        (b) If the match point in a subject started with modifier character, and
606            there was no match, the code could incorrectly back up beyond the match
607            point, and potentially beyond the first character in the subject,
608            leading to a segfault or an incorrect match result.
610    10. A conditional group with an assertion condition could lead to PCRE
611        recording an incorrect first data item for a match if no other first data
612        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
613        first data item, and therefore matched "ca" after "c" instead of at the
614        start.
616    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
617        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
619    12. The source of pcregrep now includes z/OS-specific code so that it can be
620        compiled for z/OS as part of the special z/OS distribution.
622    13. Added the -T and -TM options to pcretest.
624    14. The code in pcre_compile.c for creating the table of named capturing groups
625        has been refactored. Instead of creating the table dynamically during the
626        actual compiling pass, the information is remembered during the pre-compile
627        pass (on the stack unless there are more than 20 named groups, in which
628        case malloc() is used) and the whole table is created before the actual
629        compile happens. This has simplified the code (it is now nearly 150 lines
630        shorter) and prepared the way for better handling of references to groups
631        with duplicate names.
633    15. A back reference to a named subpattern when there is more than one of the
634        same name now checks them in the order in which they appear in the pattern.
635        The first one that is set is used for the reference. Previously only the
636        first one was inspected. This change makes PCRE more compatible with Perl.
638    16. Unicode character properties were updated from Unicode 6.3.0.
640    17. The compile-time code for auto-possessification has been refactored, based
641        on a patch by Zoltan Herczeg. It now happens after instead of during
642        compilation. The code is cleaner, and more cases are handled. The option
643        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
644        options in pcretest are provided to set it. It can also be set by
645        (*NO_AUTO_POSSESS) at the start of a pattern.
647    18. The character VT has been added to the default ("C" locale) set of
648        characters that match \s and are generally treated as white space,
649        following this same change in Perl 5.18. There is now no difference between
650        "Perl space" and "POSIX space". Whether VT is treated as white space in
651        other locales depends on the locale.
653    19. The code for checking named groups as conditions, either for being set or
654        for being recursed, has been refactored (this is related to 14 and 15
655        above). Processing unduplicated named groups should now be as fast at
656        numerical groups, and processing duplicated groups should be faster than
657        before.
659    20. Two patches to the CMake build system, by Alexander Barkov:
661          (1) Replace the "source" command by "." in CMakeLists.txt because
662              "source" is a bash-ism.
664          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
665              without these the CMake build does not work on Solaris.
667    21. Perl has changed its handling of \8 and \9. If there is no previously
668        encountered capturing group of those numbers, they are treated as the
669        literal characters 8 and 9 instead of a binary zero followed by the
670        literals. PCRE now does the same.
672    22. Following Perl, added \o{} to specify codepoints in octal, making it
673        possible to specify values greater than 0777 and also making them
674        unambiguous.
676    23. Perl now gives an error for missing closing braces after \x{... instead of
677        treating the string as literal. PCRE now does the same.
679    24. RunTest used to grumble if an inappropriate test was selected explicitly,
680        but just skip it when running all tests. This make it awkward to run ranges
681        of tests when one of them was inappropriate. Now it just skips any
682        inappropriate tests, as it always did when running all tests.
684    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
685        character types such as \d or \w, too many callouts were inserted, and the
686        data that they returned was rubbish.
688    26. In UCP mode, \s was not matching two of the characters that Perl matches,
689        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
690        were matched by \h. The code has now been refactored so that the lists of
691        the horizontal and vertical whitespace characters used for \h and \v (which
692        are defined only in one place) are now also used for \s.
694    27. Add JIT support for the 64 bit TileGX architecture.
695        Patch by Jiong Wang (Tilera Corporation).
697    28. Possessive quantifiers for classes (both explicit and automatically
698        generated) now use special opcodes instead of wrapping in ONCE brackets.
700    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
701        (because it's meaningless), this was not happening when PCRE_CASELESS was
702        set. Not wrong, but inefficient.
704    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
705        properties for \w, \d, etc) is present in a test regex. Otherwise if the
706        test contains no characters greater than 255, Perl doesn't realise it
707        should be using Unicode semantics.
709    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
710        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
711        does in Unicode mode.
713    32. Added the "forbid" facility to pcretest so that putting tests into the
714        wrong test files can sometimes be quickly detected.
716    33. There is now a limit (default 250) on the depth of nesting of parentheses.
717        This limit is imposed to control the amount of system stack used at compile
718        time. It can be changed at build time by --with-parens-nest-limit=xxx or
719        the equivalent in CMake.
721    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
722        errors. Perl warns for these when in warning mode, but PCRE has no facility
723        for giving warnings.
725    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
726        However, this was not working for (?!) because it is optimized to (*FAIL),
727        for which PCRE does not allow quantifiers. The optimization is now disabled
728        when a quantifier follows (?!). I can't see any use for this, but it makes
729        things uniform.
731    36. Perl no longer allows group names to start with digits, so I have made this
732        change also in PCRE. It simplifies the code a bit.
734    37. In extended mode, Perl ignores spaces before a + that indicates a
735        possessive quantifier. PCRE allowed a space before the quantifier, but not
736        before the possessive +. It now does.
738    38. The use of \K (reset reported match start) within a repeated possessive
739        group such as (a\Kb)*+ was not working.
741    40. Document that the same character tables must be used at compile time and
742        run time, and that the facility to pass tables to pcre_exec() and
743        pcre_dfa_exec() is for use only with saved/restored patterns.
745    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
746        features for Builds with MSVC:
748        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
749           builds). The .rc files can be used to set FileDescription and many other
750           attributes.
752        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
753           This allows higher-level build scripts which want .pdb files to avoid
754           hard-coding the exact files needed."
756    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
757        mean "start of word" and "end of word", respectively, as a transition aid.
759    43. A minimizing repeat of a class containing codepoints greater than 255 in
760        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
761        compiled to use the heap for recursion.
763    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
764        is configured.
767    Version 8.33 28-May-2013
768    ------------------------
770    1.  Added 'U' to some constants that are compared to unsigned integers, to
771        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
772        variables that are added to signed variables, to ensure the result is
773        signed and can be negated.
775    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
776        CMake config files.
778    3.  Revise the creation of config.h.generic so that all boolean macros are
779        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
780        overriding via -D on the command line possible.
782    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
783        to unsigned int is reported to make a quite noticeable speed difference in
784        a specific Windows environment. Testing on Linux did also appear to show
785        some benefit (and it is clearly not harmful). Also fixed the definition of
786        Xop which should be unsigned.
788    5.  Related to (4), changing the definition of the intermediate variable cc
789        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
790        improvements.
792    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
793        unnecessary spaces.
795    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
796        and later.
798    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
800    9.  Optimizing fast_forward_start_bits in JIT.
802    10. Adding support for callouts in JIT, and fixing some issues revealed
803        during this work. Namely:
805        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
807        (b) Minimum length was not checked before the matching is started.
809    11. The value of capture_last that is passed to callouts was incorrect in some
810        cases when there was a capture on one path that was subsequently abandoned
811        after a backtrack. Also, the capture_last value is now reset after a
812        recursion, since all captures are also reset in this case.
814    12. The interpreter no longer returns the "too many substrings" error in the
815        case when an overflowing capture is in a branch that is subsequently
816        abandoned after a backtrack.
818    13. In the pathological case when an offset vector of size 2 is used, pcretest
819        now prints out the matched string after a yield of 0 or 1.
821    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
822        Only supported by the JIT compiler at the moment.
824    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
826    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
827        offset of the starting point of the matching process, provided the offsets
828        vector is large enough.
830    17. The \A escape now records a lookbehind value of 1, though its execution
831        does not actually inspect the previous character. This is to ensure that,
832        in partial multi-segment matching, at least one character from the old
833        segment is retained when a new segment is processed. Otherwise, if there
834        are no lookbehinds in the pattern, \A might match incorrectly at the start
835        of a new segment.
837    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
839    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
840        gives some modest performance improvement in 8-bit mode.
842    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
843        be expressed in certain programming languages using Universal Character
844        Names.
846    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
847        which points out that "non characters" are not "characters that may not
848        appear in Unicode strings" but rather "characters that are reserved for
849        internal use and have only local meaning".
851    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
852        there was a conditional group that depended on an assertion, if the
853        assertion was false, the callout that immediately followed the alternation
854        in the condition was skipped when pcre_exec() was used for matching.
856    23. Allow an explicit callout to be inserted before an assertion that is the
857        condition for a conditional group, for compatibility with automatic
858        callouts, which always insert a callout at this point.
860    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
861        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
863    25. (*PRUNE) is now supported by the JIT compiler.
865    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
867    27. Fix the case where there are two or more SKIPs with arguments that may be
868        ignored.
870    28. (*SKIP) is now supported by the JIT compiler.
872    29. (*THEN) is now supported by the JIT compiler.
874    30. Update RunTest with additional test selector options.
876    31. The way PCRE handles backtracking verbs has been changed in two ways.
878        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
879        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
880        backtracking. In some cases this makes it more Perl-compatible, but Perl's
881        rather obscure rules do not always do the same thing.
883        (2) Previously, backtracking verbs were confined within assertions. This is
884        no longer the case for positive assertions, except for (*ACCEPT). Again,
885        this sometimes improves Perl compatibility, and sometimes does not.
887    32. A number of tests that were in test 2 because Perl did things differently
888        have been moved to test 1, because either Perl or PCRE has changed, and
889        these tests are now compatible.
891    32. Backtracking control verbs are now handled in the same way in JIT and
892        interpreter.
894    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
895        contained a forward subroutine reference caused a compile error.
897    34. Auto-detect and optimize limited repetitions in JIT.
899    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
900        blocking (*UTF) etc.
902    36. In the interpreter, maximizing pattern repetitions for characters and
903        character types now use tail recursion, which reduces stack usage.
905    37. The value of the max lookbehind was not correctly preserved if a compiled
906        and saved regex was reloaded on a host of different endianness.
908    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
909        of the compiled pattern block, expand the flags field from 16 to 32 bits
910        because it was almost full.
912    39. Try madvise first before posix_madvise.
914    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
915        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
916        original change locked out all matches of empty strings. This has been
917        changed so that one match of an empty string per line is recognized.
918        Subsequent searches on the same line (for colouring or for --only-matching,
919        for example) do not recognize empty strings.
921    41. Applied a user patch to fix a number of spelling mistakes in comments.
923    42. Data lines longer than 65536 caused pcretest to crash.
925    43. Clarified the data type for length and startoffset arguments for pcre_exec
926        and pcre_dfa_exec in the function-specific man pages, where they were
927        explicitly stated to be in bytes, never having been updated. I also added
928        some clarification to the pcreapi man page.
930    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
931        a segmentation fault.
934    Version 8.32 30-November-2012
935    -----------------------------
937    1.  Improved JIT compiler optimizations for first character search and single
938        character iterators.
940    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
941        Patch by Daniel Richard G.
943    3.  Single character iterator optimizations in the JIT compiler.
945    4.  Improved JIT compiler optimizations for character ranges.
947    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
948        Reported by Giuseppe D'Angelo.
950    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
951        of a line, was being set incorrectly in cases where .* appeared inside
952        atomic brackets at the start of a pattern, or where there was a subsequent
953        *PRUNE or *SKIP.
955    7.  Improved instruction cache flush for POWER/PowerPC.
956        Patch by Daniel Richard G.
958    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
959        grep:
961        (a) There is now no limit to the number of patterns to be matched.
963        (b) An error is given if a pattern is too long.
965        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
966            are now supported.
968        (d) --exclude-from and --include-from (multiple use) have been added.
970        (e) Exclusions and inclusions now apply to all files and directories, not
971            just to those obtained from scanning a directory recursively.
973        (f) Multiple uses of -f and --file-list are now supported.
975        (g) In a Windows environment, the default for -d has been changed from
976            "read" (the GNU grep default) to "skip", because otherwise the presence
977            of a directory in the file list provokes an error.
979        (h) The documentation has been revised and clarified in places.
981    9.  Improve the matching speed of capturing brackets.
983    10. Changed the meaning of \X so that it now matches a Unicode extended
984        grapheme cluster.
986    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
987        out POSIX threads when JIT support is configured.
989    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
991    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
992        structure could go wrong in environments where size_t is not the same size
993        as int.
995    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
996        set.
998    15. The EBCDIC support had decayed; later updates to the code had included
999        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
1000        general tidy up of EBCDIC-related issues, and the documentation was also
1001        not quite right. There is now a test that can be run on ASCII systems to
1002        check some of the EBCDIC-related things (but is it not a full test).
1004    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
1005        in a small tidy to the code.
1007    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
1009    18. If the --only-matching (-o) option in pcregrep is specified multiple
1010        times, each one causes appropriate output. For example, -o1 -o2 outputs the
1011        substrings matched by the 1st and 2nd capturing parentheses. A separating
1012        string can be specified by --om-separator (default empty).
1014    19. Improving the first n character searches.
1016    20. Turn case lists for horizontal and vertical white space into macros so that
1017        they are defined only once.
1019    21. This set of changes together give more compatible Unicode case-folding
1020        behaviour for characters that have more than one other case when UCP
1021        support is available.
1023        (a) The Unicode property table now has offsets into a new table of sets of
1024            three or more characters that are case-equivalent. The MultiStage2.py
1025            script that generates these tables (the pcre_ucd.c file) now scans
1026            CaseFolding.txt instead of UnicodeData.txt for character case
1027            information.
1029        (b) The code for adding characters or ranges of characters to a character
1030            class has been abstracted into a generalized function that also handles
1031            case-independence. In UTF-mode with UCP support, this uses the new data
1032            to handle characters with more than one other case.
1034        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
1035            whose other case is greater than 256 are now correctly matched
1036            caselessly. Previously, the high codepoint matched the low one, but not
1037            vice versa.
1039        (d) The processing of \h, \H, \v, and \ in character classes now makes use
1040            of the new class addition function, using character lists defined as
1041            macros alongside the case definitions of 20 above.
1043        (e) Caseless back references now work with characters that have more than
1044            one other case.
1046        (f) General caseless matching of characters with more than one other case
1047            is supported.
1049    22. Unicode character properties were updated from Unicode 6.2.0
1051    23. Improved CMake support under Windows. Patch by Daniel Richard G.
1053    24. Add support for 32-bit character strings, and UTF-32
1055    25. Major JIT compiler update (code refactoring and bugfixing).
1056        Experimental Sparc 32 support is added.
1058    26. Applied a modified version of Daniel Richard G's patch to create
1059        pcre.h.generic and config.h.generic by "make" instead of in the
1060        PrepareRelease script.
1062    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
1063        pcre_compile.c when checking for a zero character.
1065    28. Introducing a native interface for JIT. Through this interface, the compiled
1066        machine code can be directly executed. The purpose of this interface is to
1067        provide fast pattern matching, so several sanity checks are not performed.
1068        However, feature tests are still performed. The new interface provides
1069        1.4x speedup compared to the old one.
1071    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
1072        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
1073        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
1075    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
1076        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
1077        the "old" RFC 2279). Instead, it ended up passing a negative length to
1078        pcre_exec().
1080    31. Add support for GCC's visibility feature to hide internal functions.
1082    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
1083        "unknown -C option" after outputting 0 or 1.
1085    33. There is now support for generating a code coverage report for the test
1086        suite in environments where gcc is the compiler and lcov is installed. This
1087        is mainly for the benefit of the developers.
1089    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
1090        unaddressable using valgrind annotations, allowing valgrind to detect
1091        invalid memory accesses. This is mainly for the benefit of the developers.
1093    25. (*UTF) can now be used to start a pattern in any of the three libraries.
1095    26. Give configure error if --enable-cpp but no C++ compiler found.
1098    Version 8.31 06-July-2012
1099    -------------------------
1101  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
1103  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
1105  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
1106      to unsigned type, result still unsigned" that was given by an MS compiler      to unsigned type, result still unsigned" that was given by an MS compiler
1107      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
1109  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
# Line 18  Version 8.31 Line 1112  Version 8.31
1112      of more than one character:      of more than one character:
1114      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
1115          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
1116          references.          references.
1118      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
1119          subject.          subject.
1121      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
1122          characters at the end of the subject.          characters at the end of the subject.
1124      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
# Line 33  Version 8.31 Line 1127  Version 8.31
1127      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
1128          a partial match for a CR character at the end of the subject string.          a partial match for a CR character at the end of the subject string.
1130  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
1131      running pcretest, the text "(JIT)" added to the output whenever JIT is      running pcretest, the text "(JIT)" added to the output whenever JIT is
1132      actually used to run the match.      actually used to run the match.
1134  7.  Individual JIT compile options can be set in pcretest by following -s+[+]  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
1135      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
1137  8.  OP_NOT now supports any UTF character not just single-byte ones.  8.  OP_NOT now supports any UTF character not just single-byte ones.
# Line 46  Version 8.31 Line 1140  Version 8.31
1141  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
1142      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
1146  12. Applied a (slightly modified) user-supplied patch that improves performance  12. Applied a (slightly modified) user-supplied patch that improves performance
1147      when the heap is used for recursion (compiled with --disable-stack-for-      when the heap is used for recursion (compiled with --disable-stack-for-
1148      recursion). Instead of malloc and free for each heap frame each time a      recursion). Instead of malloc and free for each heap frame each time a
1149      logical recursion happens, frames are retained on a chain and re-used where      logical recursion happens, frames are retained on a chain and re-used where
1150      possible. This sometimes gives as much as 30% improvement.      possible. This sometimes gives as much as 30% improvement.
1152  13. (*COMMIT) is now correctly confined to within a recursive subpattern call.  13. As documented, (*COMMIT) is now confined to within a recursive subpattern
1153        call.
1155    14. As documented, (*COMMIT) is now confined to within a positive assertion.
1157    15. It is now possible to link pcretest with libedit as an alternative to
1158        libreadline.
1160    16. (*COMMIT) control verb is now supported by the JIT compiler.
1162    17. The Unicode data tables have been updated to Unicode 6.1.0.
1164    18. Added --file-list option to pcregrep.
1166    19. Added binary file support to pcregrep, including the -a, --binary-files,
1167        -I, and --text options.
1169    20. The madvise function is renamed for posix_madvise for QNX compatibility
1170        reasons. Fixed by Giuseppe D'Angelo.
1172    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
1174    22. Changed the option for creating symbolic links for 16-bit man pages from
1175        -s to -sf so that re-installing does not cause issues.
1177    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
1179    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
1180        matches in certain environments (the workspace was not being correctly
1181        retained). Also added to pcre_dfa_exec() a simple plausibility check on
1182        some of the workspace data at the beginning of a restart.
1184    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
1185        was not doing so when it should - probably a typo introduced by SVN 528
1186        (change 8.10/14).
1188    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
1189        \w+ when the character tables indicated that \x{c4} was a word character.
1190        There were several related cases, all because the tests for doing a table
1191        lookup were testing for characters less than 127 instead of 255.
1193    27. If a pattern contains capturing parentheses that are not used in a match,
1194        their slots in the ovector are set to -1. For those that are higher than
1195        any matched groups, this happens at the end of processing. In the case when
1196        there were back references that the ovector was too small to contain
1197        (causing temporary malloc'd memory to be used during matching), and the
1198        highest capturing number was not used, memory off the end of the ovector
1199        was incorrectly being set to -1. (It was using the size of the temporary
1200        memory instead of the true size.)
1202    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
1203        ovector size, it uses memory at the end of the block that it has got.
1205    29. Check for an overlong MARK name and give an error at compile time. The
1206        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
1208    30. JIT compiler update.
1210    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
1211        Rill for the patch.
1213    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
1215    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
1217    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
1218        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
1219        was enabled.
1221    35. Improve JIT code generation for greedy plus quantifier.
1223    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
1224        1 to "aa" instead of to an empty string. The bug affected repeated groups
1225        that could potentially match an empty string.
1227    37. Optimizing single character iterators in JIT.
1229    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
1230        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
1231        codepoints that are too big for the mode are faulted, and in a UTF mode,
1232        disallowed codepoints are also faulted.
1234    39. If PCRE was compiled with UTF support, in three places in the DFA
1235        matcher there was code that should only have been obeyed in UTF mode, but
1236        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
1237        processing when bytes with values greater than 127 were present. In 16-bit
1238        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
1239        both cases the values are those that cannot be the first data item in a UTF
1240        character. The three items that might have provoked this were recursions,
1241        possessively repeated groups, and atomic groups.
1243    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
1244        and pcregrep, because some OS require shared objects to be explicitly
1245        passed to ld, causing the link step to fail if they are not.
1247    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
1248        mode, patterns that started with \h* or \R* might be incorrectly matched.
1251  Version 8.30 04-February-2012  Version 8.30 04-February-2012
# Line 1248  Version 7.9 11-Apr-09 Line 2438  Version 7.9 11-Apr-09
2438  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
2439      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
2440      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2441      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2442        8.33.]
2444  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
2445      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 1491  Version 7.7 07-May-08 Line 2682  Version 7.7 07-May-08
2682      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2683      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2684      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2685      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2686      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2687      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.934  
changed lines
  Added in v.1606

  ViewVC Help
Powered by ViewVC 1.1.5