/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.753  
changed lines
  Added in v.1558

  ViewVC Help
Powered by ViewVC 1.1.5