ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 989 by zherczeg, Sat Jul 7 11:11:02 2012 UTC revision 1557 by ph10, Fri May 8 16:39:40 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.32  Version 8.38 xx-xxx-xxxx
5  ------------  ------------------------
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.
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.
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.
23    Version 8.37 28-April-2015
24    --------------------------
26    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
27        for those parentheses to be closed with whatever has been captured so far.
28        However, it was failing to mark any other groups between the hightest
29        capture so far and the currrent group as "unset". Thus, the ovector for
30        those groups contained whatever was previously there. An example is the
31        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
33    2.  If an assertion condition was quantified with a minimum of zero (an odd
34        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
36    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
37        unrecognized modifier, a crash could occur.
39    4.  An attempt to do global matching in pcretest with a zero-length ovector
40        caused a crash.
42    5.  Fixed a memory leak during matching that could occur for a subpattern
43        subroutine call (recursive or otherwise) if the number of captured groups
44        that had to be saved was greater than ten.
46    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
47        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
48        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
50    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
51        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
53    8. When a pattern is compiled, it remembers the highest back reference so that
54       when matching, if the ovector is too small, extra memory can be obtained to
55       use instead. A conditional subpattern whose condition is a check on a
56       capture having happened, such as, for example in the pattern
57       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
58       setting the highest backreference number. This mattered only if pcre_exec()
59       was called with an ovector that was too small to hold the capture, and there
60       was no other kind of back reference (a situation which is probably quite
61       rare). The effect of the bug was that the condition was always treated as
62       FALSE when the capture could not be consulted, leading to a incorrect
63       behaviour by pcre_exec(). This bug has been fixed.
65    9. A reference to a duplicated named group (either a back reference or a test
66       for being set in a conditional) that occurred in a part of the pattern where
67       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
68       to be incorrectly calculated, leading to overwriting.
70    10. A mutually recursive set of back references such as (\2)(\1) caused a
71        segfault at study time (while trying to find the minimum matching length).
72        The infinite loop is now broken (with the minimum length unset, that is,
73        zero).
75    11. If an assertion that was used as a condition was quantified with a minimum
76        of zero, matching went wrong. In particular, if the whole group had
77        unlimited repetition and could match an empty string, a segfault was
78        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
79        assertions to be quantified, but not if they are being used as conditions,
80        so the above pattern is faulted by Perl. PCRE has now been changed so that
81        it also rejects such patterns.
83    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
84        failed to allow the zero-repeat case if pcre2_exec() was called with an
85        ovector too small to capture the group.
87    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
88        Red Hat Product Security:
90        (a) A crash if /K and /F were both set with the option to save the compiled
91        pattern.
93        (b) Another crash if the option to print captured substrings in a callout
94        was combined with setting a null ovector, for example \O\C+ as a subject
95        string.
97    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
98        forward reference repeated a large (but limited) number of times within a
99        repeated outer group that has a zero minimum quantifier, caused incorrect
100        code to be compiled, leading to the error "internal error:
101        previously-checked referenced subpattern not found" when an incorrect
102        memory address was read. This bug was reported as "heap overflow",
103        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
104        CVE-2015-2325.
106    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
107        call within a group that also contained a recursive back reference caused
108        incorrect code to be compiled. This bug was reported as "heap overflow",
109        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
110        number CVE-2015-2326.
112    24. Computing the size of the JIT read-only data in advance has been a source
113        of various issues, and new ones are still appear unfortunately. To fix
114        existing and future issues, size computation is eliminated from the code,
115        and replaced by on-demand memory allocation.
117    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
118        adjacent to the end of the range, and the range contained characters with
119        more than one other case, caused incorrect behaviour when compiled in UTF
120        mode. In that example, the range a-j was left out of the class.
122    26. Fix JIT compilation of conditional blocks, which assertion
123        is converted to (*FAIL). E.g: /(?(?!))/.
125    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
126        discovered by the LLVM fuzzer.
128    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
129        when this assertion was used as a condition, for example (?(?!)a|b). In
130        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
131        error about an unsupported item.
133    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
134        possessification code could take exponential time to complete. A recursion
135        depth limit of 1000 has been imposed to limit the resources used by this
136        optimization.
138    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
139        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
140        because \S ensures they are all in the class. The code for doing this was
141        interacting badly with the code for computing the amount of space needed to
142        compile the pattern, leading to a buffer overflow. This bug was discovered
143        by the LLVM fuzzer.
145    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
146        other kinds of group caused stack overflow at compile time. This bug was
147        discovered by the LLVM fuzzer.
149    32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
150        between a subroutine call and its quantifier was incorrectly compiled,
151        leading to buffer overflow or other errors. This bug was discovered by the
152        LLVM fuzzer.
154    33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
155        assertion after (?(. The code was failing to check the character after
156        (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
157        was discovered by the LLVM fuzzer.
159    34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
160        a fixed maximum following a group that contains a subroutine reference was
161        incorrectly compiled and could trigger buffer overflow. This bug was
162        discovered by the LLVM fuzzer.
164    35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
165        caused a stack overflow instead of the diagnosis of a non-fixed length
166        lookbehind assertion. This bug was discovered by the LLVM fuzzer.
168    36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
169        (e.g. /(?<=\Ka)/) could make pcregrep loop.
171    37. There was a similar problem to 36 in pcretest for global matches.
173    38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
174        and a subsequent item in the pattern caused a non-match, backtracking over
175        the repeated \X did not stop, but carried on past the start of the subject,
176        causing reference to random memory and/or a segfault. There were also some
177        other cases where backtracking after \C could crash. This set of bugs was
178        discovered by the LLVM fuzzer.
180    39. The function for finding the minimum length of a matching string could take
181        a very long time if mutual recursion was present many times in a pattern,
182        for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
183        method has been implemented. This infelicity was discovered by the LLVM
184        fuzzer.
186    40. Static linking against the PCRE library using the pkg-config module was
187        failing on missing pthread symbols.
190    Version 8.36 26-September-2014
191    ------------------------------
193    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
194        -Wmissing-field-initializers and -Wunused-parameter.
196    2.  The tests for quantifiers being too big (greater than 65535) were being
197        applied after reading the number, and stupidly assuming that integer
198        overflow would give a negative number. The tests are now applied as the
199        numbers are read.
201    3.  Tidy code in pcre_exec.c where two branches that used to be different are
202        now the same.
204    4.  The JIT compiler did not generate match limit checks for certain
205        bracketed expressions with quantifiers. This may lead to exponential
206        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
207        issue should be resolved now.
209    5.  Fixed an issue, which occures when nested alternatives are optimized
210        with table jumps.
212    6.  Inserted two casts and changed some ints to size_t in the light of some
213        reported 64-bit compiler warnings (Bugzilla 1477).
215    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
216        an empty string, which sometimes were behaving incorrectly in the
217        interpreter (though correctly in the JIT matcher). This pcretest input is
218        an example:
220          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
223        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
224        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
225        for an empty string was breaking the inner loop and carrying on at a lower
226        level, when possessive repeated groups should always return to a higher
227        level as they have no backtrack points in them. The empty string test now
228        occurs at the outer level.
230    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
231        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
233    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
234        doesn't).
236    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
237        to hold a pattern to be incorrectly computed (too small) when there were
238        named back references to duplicated names. This could cause "internal
239        error: code overflow" or "double free or corruption" or other memory
240        handling errors.
242    11. When named subpatterns had the same prefixes, back references could be
243        confused. For example, in this pattern:
245          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
247        the reference to 'Name' was incorrectly treated as a reference to a
248        duplicate name.
250    12. A pattern such as /^s?c/mi8 where the optional character has more than
251        one "other case" was incorrectly compiled such that it would only try to
252        match starting at "c".
254    13. When a pattern starting with \s was studied, VT was not included in the
255        list of possible starting characters; this should have been part of the
256        8.34/18 patch.
258    14. If a character class started [\Qx]... where x is any character, the class
259        was incorrectly terminated at the ].
261    15. If a pattern that started with a caseless match for a character with more
262        than one "other case" was studied, PCRE did not set up the starting code
263        unit bit map for the list of possible characters. Now it does. This is an
264        optimization improvement, not a bug fix.
266    16. The Unicode data tables have been updated to Unicode 7.0.0.
268    17. Fixed a number of memory leaks in pcregrep.
270    18. Avoid a compiler warning (from some compilers) for a function call with
271        a cast that removes "const" from an lvalue by using an intermediate
272        variable (to which the compiler does not object).
274    19. Incorrect code was compiled if a group that contained an internal recursive
275        back reference was optional (had quantifier with a minimum of zero). This
276        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
277        caused segmentation faults because of stack overflows at compile time.
279    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
280        group that is quantified with an indefinite repeat, caused a compile-time
281        loop which used up all the system stack and provoked a segmentation fault.
282        This was not the same bug as 19 above.
284    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
285        Patch by Mike Frysinger.
288    Version 8.35 04-April-2014
289    --------------------------
291    1.  A new flag is set, when property checks are present in an XCLASS.
292        When this flag is not set, PCRE can perform certain optimizations
293        such as studying these XCLASS-es.
295    2.  The auto-possessification of character sets were improved: a normal
296        and an extended character set can be compared now. Furthermore
297        the JIT compiler optimizes more character set checks.
299    3.  Got rid of some compiler warnings for potentially uninitialized variables
300        that show up only when compiled with -O2.
302    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
303        of a match later then the end of the match. The pcretest program was not
304        handling the case sensibly - it was outputting from the start to the next
305        binary zero. It now reports this situation in a message, and outputs the
306        text from the end to the start.
308    5.  Fast forward search is improved in JIT. Instead of the first three
309        characters, any three characters with fixed position can be searched.
310        Search order: first, last, middle.
312    6.  Improve character range checks in JIT. Characters are read by an inprecise
313        function now, which returns with an unknown value if the character code is
314        above a certain threshold (e.g: 256). The only limitation is that the value
315        must be bigger than the threshold as well. This function is useful when
316        the characters above the threshold are handled in the same way.
318    7.  The macros whose names start with RAWUCHAR are placeholders for a future
319        mode in which only the bottom 21 bits of 32-bit data items are used. To
320        make this more memorable for those maintaining the code, the names have
321        been changed to start with UCHAR21, and an extensive comment has been added
322        to their definition.
324    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
325        to the export list in Makefile.am (they were accidentally omitted from the
326        8.34 tarball).
328    9.  The informational output from pcretest used the phrase "starting byte set"
329        which is inappropriate for the 16-bit and 32-bit libraries. As the output
330        for "first char" and "need char" really means "non-UTF-char", I've changed
331        "byte" to "char", and slightly reworded the output. The documentation about
332        these values has also been (I hope) clarified.
334    10. Another JIT related optimization: use table jumps for selecting the correct
335        backtracking path, when more than four alternatives are present inside a
336        bracket.
338    11. Empty match is not possible, when the minimum length is greater than zero,
339        and there is no \K in the pattern. JIT should avoid empty match checks in
340        such cases.
342    12. In a caseless character class with UCP support, when a character with more
343        than one alternative case was not the first character of a range, not all
344        the alternative cases were added to the class. For example, s and \x{17f}
345        are both alternative cases for S: the class [RST] was handled correctly,
346        but [R-T] was not.
348    13. The configure.ac file always checked for pthread support when JIT was
349        enabled. This is not used in Windows, so I have put this test inside a
350        check for the presence of windows.h (which was already tested for).
352    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
353        The algorithm provides a way to skip certain starting offsets, and usually
354        faster than linear prefix searches.
356    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
357        as for 'fr_FR' and 'french'. For some reason, however, it then used the
358        Windows-specific input and output files, which have 'french' screwed in.
359        So this could never have worked. One of the problems with locales is that
360        they aren't always the same. I have now updated RunTest so that it checks
361        the output of the locale test (test 3) against three different output
362        files, and it allows the test to pass if any one of them matches. With luck
363        this should make the test pass on some versions of Solaris where it was
364        failing. Because of the uncertainty, the script did not used to stop if
365        test 3 failed; it now does. If further versions of a French locale ever
366        come to light, they can now easily be added.
368    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
369        there was a message during ./configure, but it did not stop. This now
370        provokes an error. The invalid example in README has been corrected.
371        If a value less than the minimum is given, the minimum value has always
372        been used, but now a warning is given.
374    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
375        was a bug in the test system, which is now fixed. Also, the list of various
376        configurations that are tested for each release did not have one with both
377        16/32 bits and --enable-bar-anycrlf. It now does.
379    18. pcretest was missing "-C bsr" for displaying the \R default setting.
381    19. Little endian PowerPC systems are supported now by the JIT compiler.
383    20. The fast forward newline mechanism could enter to an infinite loop on
384        certain invalid UTF-8 input. Although we don't support these cases
385        this issue can be fixed by a performance optimization.
387    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
388        not take account if existing stack usage. There is now a new global
389        variable called pcre_stack_guard that can be set to point to an external
390        function to check stack availability. It is called at the start of
391        processing every parenthesized group.
393    22. A typo in the code meant that in ungreedy mode the max/min qualifier
394        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
395        not match "ab".
397    23. When UTF was disabled, the JIT program reported some incorrect compile
398        errors. These messages are silenced now.
400    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
401        compiler.
403    25. Change all the temporary files used in RunGrepTest to be different to those
404        used by RunTest so that the tests can be run simultaneously, for example by
405        "make -j check".
408    Version 8.34 15-December-2013
409    -----------------------------
411    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
412        executable memory. Patch inspired by Carsten Klein.
414    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
415        this macro is never tested and has no effect, because the work to support
416        coverage involves only compiling and linking options and special targets in
417        the Makefile. The comment in config.h implied that defining the macro would
418        enable coverage support, which is totally false. There was also support for
419        setting this macro in the CMake files (my fault, I just copied it from
420        configure). SUPPORT_GCOV has now been removed.
422    3.  Make a small performance improvement in strlen16() and strlen32() in
423        pcretest.
425    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
426        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
427        these cases). There was also one in pcretest.c.
429    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
431    6.  In UTF mode, the code for checking whether a group could match an empty
432        string (which is used for indefinitely repeated groups to allow for
433        breaking an infinite loop) was broken when the group contained a repeated
434        negated single-character class with a character that occupied more than one
435        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
436        UTF-8 mode). The effect was undefined: the group might or might not be
437        deemed as matching an empty string, or the program might have crashed.
439    7.  The code for checking whether a group could match an empty string was not
440        recognizing that \h, \H, \v, \V, and \R must match a character.
442    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
443        an empty string. If it can, pcretest shows this in its information output.
445    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
446        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
447        matched by pcre_exec() without using JIT:
449        (a) If the rest of the pattern did not match after a maximal run of
450            grapheme clusters, the code for backing up to try with fewer of them
451            did not always back up over a full grapheme when characters that do not
452            have the modifier quality were involved, e.g. Hangul syllables.
454        (b) If the match point in a subject started with modifier character, and
455            there was no match, the code could incorrectly back up beyond the match
456            point, and potentially beyond the first character in the subject,
457            leading to a segfault or an incorrect match result.
459    10. A conditional group with an assertion condition could lead to PCRE
460        recording an incorrect first data item for a match if no other first data
461        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
462        first data item, and therefore matched "ca" after "c" instead of at the
463        start.
465    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
466        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
468    12. The source of pcregrep now includes z/OS-specific code so that it can be
469        compiled for z/OS as part of the special z/OS distribution.
471    13. Added the -T and -TM options to pcretest.
473    14. The code in pcre_compile.c for creating the table of named capturing groups
474        has been refactored. Instead of creating the table dynamically during the
475        actual compiling pass, the information is remembered during the pre-compile
476        pass (on the stack unless there are more than 20 named groups, in which
477        case malloc() is used) and the whole table is created before the actual
478        compile happens. This has simplified the code (it is now nearly 150 lines
479        shorter) and prepared the way for better handling of references to groups
480        with duplicate names.
482    15. A back reference to a named subpattern when there is more than one of the
483        same name now checks them in the order in which they appear in the pattern.
484        The first one that is set is used for the reference. Previously only the
485        first one was inspected. This change makes PCRE more compatible with Perl.
487    16. Unicode character properties were updated from Unicode 6.3.0.
489    17. The compile-time code for auto-possessification has been refactored, based
490        on a patch by Zoltan Herczeg. It now happens after instead of during
491        compilation. The code is cleaner, and more cases are handled. The option
492        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
493        options in pcretest are provided to set it. It can also be set by
494        (*NO_AUTO_POSSESS) at the start of a pattern.
496    18. The character VT has been added to the default ("C" locale) set of
497        characters that match \s and are generally treated as white space,
498        following this same change in Perl 5.18. There is now no difference between
499        "Perl space" and "POSIX space". Whether VT is treated as white space in
500        other locales depends on the locale.
502    19. The code for checking named groups as conditions, either for being set or
503        for being recursed, has been refactored (this is related to 14 and 15
504        above). Processing unduplicated named groups should now be as fast at
505        numerical groups, and processing duplicated groups should be faster than
506        before.
508    20. Two patches to the CMake build system, by Alexander Barkov:
510          (1) Replace the "source" command by "." in CMakeLists.txt because
511              "source" is a bash-ism.
513          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
514              without these the CMake build does not work on Solaris.
516    21. Perl has changed its handling of \8 and \9. If there is no previously
517        encountered capturing group of those numbers, they are treated as the
518        literal characters 8 and 9 instead of a binary zero followed by the
519        literals. PCRE now does the same.
521    22. Following Perl, added \o{} to specify codepoints in octal, making it
522        possible to specify values greater than 0777 and also making them
523        unambiguous.
525    23. Perl now gives an error for missing closing braces after \x{... instead of
526        treating the string as literal. PCRE now does the same.
528    24. RunTest used to grumble if an inappropriate test was selected explicitly,
529        but just skip it when running all tests. This make it awkward to run ranges
530        of tests when one of them was inappropriate. Now it just skips any
531        inappropriate tests, as it always did when running all tests.
533    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
534        character types such as \d or \w, too many callouts were inserted, and the
535        data that they returned was rubbish.
537    26. In UCP mode, \s was not matching two of the characters that Perl matches,
538        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
539        were matched by \h. The code has now been refactored so that the lists of
540        the horizontal and vertical whitespace characters used for \h and \v (which
541        are defined only in one place) are now also used for \s.
543    27. Add JIT support for the 64 bit TileGX architecture.
544        Patch by Jiong Wang (Tilera Corporation).
546    28. Possessive quantifiers for classes (both explicit and automatically
547        generated) now use special opcodes instead of wrapping in ONCE brackets.
549    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
550        (because it's meaningless), this was not happening when PCRE_CASELESS was
551        set. Not wrong, but inefficient.
553    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
554        properties for \w, \d, etc) is present in a test regex. Otherwise if the
555        test contains no characters greater than 255, Perl doesn't realise it
556        should be using Unicode semantics.
558    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
559        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
560        does in Unicode mode.
562    32. Added the "forbid" facility to pcretest so that putting tests into the
563        wrong test files can sometimes be quickly detected.
565    33. There is now a limit (default 250) on the depth of nesting of parentheses.
566        This limit is imposed to control the amount of system stack used at compile
567        time. It can be changed at build time by --with-parens-nest-limit=xxx or
568        the equivalent in CMake.
570    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
571        errors. Perl warns for these when in warning mode, but PCRE has no facility
572        for giving warnings.
574    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
575        However, this was not working for (?!) because it is optimized to (*FAIL),
576        for which PCRE does not allow quantifiers. The optimization is now disabled
577        when a quantifier follows (?!). I can't see any use for this, but it makes
578        things uniform.
580    36. Perl no longer allows group names to start with digits, so I have made this
581        change also in PCRE. It simplifies the code a bit.
583    37. In extended mode, Perl ignores spaces before a + that indicates a
584        possessive quantifier. PCRE allowed a space before the quantifier, but not
585        before the possessive +. It now does.
587    38. The use of \K (reset reported match start) within a repeated possessive
588        group such as (a\Kb)*+ was not working.
590    40. Document that the same character tables must be used at compile time and
591        run time, and that the facility to pass tables to pcre_exec() and
592        pcre_dfa_exec() is for use only with saved/restored patterns.
594    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
595        features for Builds with MSVC:
597        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
598           builds). The .rc files can be used to set FileDescription and many other
599           attributes.
601        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
602           This allows higher-level build scripts which want .pdb files to avoid
603           hard-coding the exact files needed."
605    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
606        mean "start of word" and "end of word", respectively, as a transition aid.
608    43. A minimizing repeat of a class containing codepoints greater than 255 in
609        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
610        compiled to use the heap for recursion.
612    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
613        is configured.
616    Version 8.33 28-May-2013
617    ------------------------
619    1.  Added 'U' to some constants that are compared to unsigned integers, to
620        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
621        variables that are added to signed variables, to ensure the result is
622        signed and can be negated.
624    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
625        CMake config files.
627    3.  Revise the creation of config.h.generic so that all boolean macros are
628        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
629        overriding via -D on the command line possible.
631    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
632        to unsigned int is reported to make a quite noticeable speed difference in
633        a specific Windows environment. Testing on Linux did also appear to show
634        some benefit (and it is clearly not harmful). Also fixed the definition of
635        Xop which should be unsigned.
637    5.  Related to (4), changing the definition of the intermediate variable cc
638        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
639        improvements.
641    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
642        unnecessary spaces.
644    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
645        and later.
647    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
649    9.  Optimizing fast_forward_start_bits in JIT.
651    10. Adding support for callouts in JIT, and fixing some issues revealed
652        during this work. Namely:
654        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
656        (b) Minimum length was not checked before the matching is started.
658    11. The value of capture_last that is passed to callouts was incorrect in some
659        cases when there was a capture on one path that was subsequently abandoned
660        after a backtrack. Also, the capture_last value is now reset after a
661        recursion, since all captures are also reset in this case.
663    12. The interpreter no longer returns the "too many substrings" error in the
664        case when an overflowing capture is in a branch that is subsequently
665        abandoned after a backtrack.
667    13. In the pathological case when an offset vector of size 2 is used, pcretest
668        now prints out the matched string after a yield of 0 or 1.
670    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
671        Only supported by the JIT compiler at the moment.
673    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
675    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
676        offset of the starting point of the matching process, provided the offsets
677        vector is large enough.
679    17. The \A escape now records a lookbehind value of 1, though its execution
680        does not actually inspect the previous character. This is to ensure that,
681        in partial multi-segment matching, at least one character from the old
682        segment is retained when a new segment is processed. Otherwise, if there
683        are no lookbehinds in the pattern, \A might match incorrectly at the start
684        of a new segment.
686    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
688    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
689        gives some modest performance improvement in 8-bit mode.
691    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
692        be expressed in certain programming languages using Universal Character
693        Names.
695    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
696        which points out that "non characters" are not "characters that may not
697        appear in Unicode strings" but rather "characters that are reserved for
698        internal use and have only local meaning".
700    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
701        there was a conditional group that depended on an assertion, if the
702        assertion was false, the callout that immediately followed the alternation
703        in the condition was skipped when pcre_exec() was used for matching.
705    23. Allow an explicit callout to be inserted before an assertion that is the
706        condition for a conditional group, for compatibility with automatic
707        callouts, which always insert a callout at this point.
709    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
710        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
712    25. (*PRUNE) is now supported by the JIT compiler.
714    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
716    27. Fix the case where there are two or more SKIPs with arguments that may be
717        ignored.
719    28. (*SKIP) is now supported by the JIT compiler.
721    29. (*THEN) is now supported by the JIT compiler.
723    30. Update RunTest with additional test selector options.
725    31. The way PCRE handles backtracking verbs has been changed in two ways.
727        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
728        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
729        backtracking. In some cases this makes it more Perl-compatible, but Perl's
730        rather obscure rules do not always do the same thing.
732        (2) Previously, backtracking verbs were confined within assertions. This is
733        no longer the case for positive assertions, except for (*ACCEPT). Again,
734        this sometimes improves Perl compatibility, and sometimes does not.
736    32. A number of tests that were in test 2 because Perl did things differently
737        have been moved to test 1, because either Perl or PCRE has changed, and
738        these tests are now compatible.
740    32. Backtracking control verbs are now handled in the same way in JIT and
741        interpreter.
743    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
744        contained a forward subroutine reference caused a compile error.
746    34. Auto-detect and optimize limited repetitions in JIT.
748    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
749        blocking (*UTF) etc.
751    36. In the interpreter, maximizing pattern repetitions for characters and
752        character types now use tail recursion, which reduces stack usage.
754    37. The value of the max lookbehind was not correctly preserved if a compiled
755        and saved regex was reloaded on a host of different endianness.
757    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
758        of the compiled pattern block, expand the flags field from 16 to 32 bits
759        because it was almost full.
761    39. Try madvise first before posix_madvise.
763    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
764        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
765        original change locked out all matches of empty strings. This has been
766        changed so that one match of an empty string per line is recognized.
767        Subsequent searches on the same line (for colouring or for --only-matching,
768        for example) do not recognize empty strings.
770    41. Applied a user patch to fix a number of spelling mistakes in comments.
772    42. Data lines longer than 65536 caused pcretest to crash.
774    43. Clarified the data type for length and startoffset arguments for pcre_exec
775        and pcre_dfa_exec in the function-specific man pages, where they were
776        explicitly stated to be in bytes, never having been updated. I also added
777        some clarification to the pcreapi man page.
779    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
780        a segmentation fault.
783    Version 8.32 30-November-2012
784    -----------------------------
786  1.  Improved JIT compiler optimizations for first character search and single  1.  Improved JIT compiler optimizations for first character search and single
787      character iterators.      character iterators.
# Line 12  Version 8.32 Line 791  Version 8.32
792  3.  Single character iterator optimizations in the JIT compiler.  3.  Single character iterator optimizations in the JIT compiler.
794    4.  Improved JIT compiler optimizations for character ranges.
796    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
797        Reported by Giuseppe D'Angelo.
799    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
800        of a line, was being set incorrectly in cases where .* appeared inside
801        atomic brackets at the start of a pattern, or where there was a subsequent
802        *PRUNE or *SKIP.
804    7.  Improved instruction cache flush for POWER/PowerPC.
805        Patch by Daniel Richard G.
807    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
808        grep:
810        (a) There is now no limit to the number of patterns to be matched.
812        (b) An error is given if a pattern is too long.
814        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
815            are now supported.
817        (d) --exclude-from and --include-from (multiple use) have been added.
819        (e) Exclusions and inclusions now apply to all files and directories, not
820            just to those obtained from scanning a directory recursively.
822        (f) Multiple uses of -f and --file-list are now supported.
824        (g) In a Windows environment, the default for -d has been changed from
825            "read" (the GNU grep default) to "skip", because otherwise the presence
826            of a directory in the file list provokes an error.
828        (h) The documentation has been revised and clarified in places.
830    9.  Improve the matching speed of capturing brackets.
832    10. Changed the meaning of \X so that it now matches a Unicode extended
833        grapheme cluster.
835    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
836        out POSIX threads when JIT support is configured.
838    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
840    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
841        structure could go wrong in environments where size_t is not the same size
842        as int.
844    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
845        set.
847    15. The EBCDIC support had decayed; later updates to the code had included
848        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
849        general tidy up of EBCDIC-related issues, and the documentation was also
850        not quite right. There is now a test that can be run on ASCII systems to
851        check some of the EBCDIC-related things (but is it not a full test).
853    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
854        in a small tidy to the code.
856    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
858    18. If the --only-matching (-o) option in pcregrep is specified multiple
859        times, each one causes appropriate output. For example, -o1 -o2 outputs the
860        substrings matched by the 1st and 2nd capturing parentheses. A separating
861        string can be specified by --om-separator (default empty).
863    19. Improving the first n character searches.
865    20. Turn case lists for horizontal and vertical white space into macros so that
866        they are defined only once.
868    21. This set of changes together give more compatible Unicode case-folding
869        behaviour for characters that have more than one other case when UCP
870        support is available.
872        (a) The Unicode property table now has offsets into a new table of sets of
873            three or more characters that are case-equivalent. The MultiStage2.py
874            script that generates these tables (the pcre_ucd.c file) now scans
875            CaseFolding.txt instead of UnicodeData.txt for character case
876            information.
878        (b) The code for adding characters or ranges of characters to a character
879            class has been abstracted into a generalized function that also handles
880            case-independence. In UTF-mode with UCP support, this uses the new data
881            to handle characters with more than one other case.
883        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
884            whose other case is greater than 256 are now correctly matched
885            caselessly. Previously, the high codepoint matched the low one, but not
886            vice versa.
888        (d) The processing of \h, \H, \v, and \ in character classes now makes use
889            of the new class addition function, using character lists defined as
890            macros alongside the case definitions of 20 above.
892        (e) Caseless back references now work with characters that have more than
893            one other case.
895        (f) General caseless matching of characters with more than one other case
896            is supported.
898    22. Unicode character properties were updated from Unicode 6.2.0
900    23. Improved CMake support under Windows. Patch by Daniel Richard G.
902    24. Add support for 32-bit character strings, and UTF-32
904    25. Major JIT compiler update (code refactoring and bugfixing).
905        Experimental Sparc 32 support is added.
907    26. Applied a modified version of Daniel Richard G's patch to create
908        pcre.h.generic and config.h.generic by "make" instead of in the
909        PrepareRelease script.
911    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
912        pcre_compile.c when checking for a zero character.
914    28. Introducing a native interface for JIT. Through this interface, the compiled
915        machine code can be directly executed. The purpose of this interface is to
916        provide fast pattern matching, so several sanity checks are not performed.
917        However, feature tests are still performed. The new interface provides
918        1.4x speedup compared to the old one.
920    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
921        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
922        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
924    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
925        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
926        the "old" RFC 2279). Instead, it ended up passing a negative length to
927        pcre_exec().
929    31. Add support for GCC's visibility feature to hide internal functions.
931    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
932        "unknown -C option" after outputting 0 or 1.
934    33. There is now support for generating a code coverage report for the test
935        suite in environments where gcc is the compiler and lcov is installed. This
936        is mainly for the benefit of the developers.
938    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
939        unaddressable using valgrind annotations, allowing valgrind to detect
940        invalid memory accesses. This is mainly for the benefit of the developers.
942    25. (*UTF) can now be used to start a pattern in any of the three libraries.
944    26. Give configure error if --enable-cpp but no C++ compiler found.
947  Version 8.31 06-July-2012  Version 8.31 06-July-2012
948  -------------------------  -------------------------
# Line 1356  Version 7.9 11-Apr-09 Line 2287  Version 7.9 11-Apr-09
2287  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
2288      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
2289      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2290      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2291        8.33.]
2293  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
2294      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 1599  Version 7.7 07-May-08 Line 2531  Version 7.7 07-May-08
2531      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2532      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2533      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2534      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2535      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2536      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.989  
changed lines
  Added in v.1557

  ViewVC Help
Powered by ViewVC 1.1.5