ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 934 by ph10, Sat Feb 25 12:30:36 2012 UTC revision 1537 by ph10, Fri Mar 27 17:48:28 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.31  Version 8.37 xx-xxx-2015
5    ------------------------
7    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
8        for those parentheses to be closed with whatever has been captured so far.
9        However, it was failing to mark any other groups between the hightest
10        capture so far and the currrent group as "unset". Thus, the ovector for
11        those groups contained whatever was previously there. An example is the
12        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
14    2.  If an assertion condition was quantified with a minimum of zero (an odd
15        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
17    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
18        unrecognized modifier, a crash could occur.
20    4.  An attempt to do global matching in pcretest with a zero-length ovector
21        caused a crash.
23    5.  Fixed a memory leak during matching that could occur for a subpattern
24        subroutine call (recursive or otherwise) if the number of captured groups
25        that had to be saved was greater than ten.
27    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
28        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
29        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
31    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
32        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
34    8. When a pattern is compiled, it remembers the highest back reference so that
35       when matching, if the ovector is too small, extra memory can be obtained to
36       use instead. A conditional subpattern whose condition is a check on a
37       capture having happened, such as, for example in the pattern
38       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
39       setting the highest backreference number. This mattered only if pcre_exec()
40       was called with an ovector that was too small to hold the capture, and there
41       was no other kind of back reference (a situation which is probably quite
42       rare). The effect of the bug was that the condition was always treated as
43       FALSE when the capture could not be consulted, leading to a incorrect
44       behaviour by pcre2_match(). This bug has been fixed.
46    9. A reference to a duplicated named group (either a back reference or a test
47       for being set in a conditional) that occurred in a part of the pattern where
48       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
49       to be incorrectly calculated, leading to overwriting.
51    10. A mutually recursive set of back references such as (\2)(\1) caused a
52        segfault at study time (while trying to find the minimum matching length).
53        The infinite loop is now broken (with the minimum length unset, that is,
54        zero).
56    11. If an assertion that was used as a condition was quantified with a minimum
57        of zero, matching went wrong. In particular, if the whole group had
58        unlimited repetition and could match an empty string, a segfault was
59        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
60        assertions to be quantified, but not if they are being used as conditions,
61        so the above pattern is faulted by Perl. PCRE has now been changed so that
62        it also rejects such patterns.
64    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
65        failed to allow the zero-repeat case if pcre2_exec() was called with an
66        ovector too small to capture the group.
68    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
69        Red Hat Product Security:
71        (a) A crash if /K and /F were both set with the option to save the compiled
72        pattern.
74        (b) Another crash if the option to print captured substrings in a callout
75        was combined with setting a null ovector, for example \O\C+ as a subject
76        string.
78    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
79        forward reference repeated a large (but limited) number of times within a
80        repeated outer group that has a zero minimum quantifier, caused incorrect
81        code to be compiled, leading to the error "internal error:
82        previously-checked referenced subpattern not found" when an incorrect
83        memory address was read. This bug was reported as "heap overflow",
84        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
85        CVE-2015-2325.
87    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
88        call within a group that also contained a recursive back reference caused
89        incorrect code to be compiled. This bug was reported as "heap overflow",
90        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
91        number CVE-2015-2326.
93    24. Computing the size of the JIT read-only data in advance has been a source
94        of various issues, and new ones are still appear unfortunately. To fix
95        existing and future issues, size computation is eliminated from the code,
96        and replaced by on-demand memory allocation.
98    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
99        adjacent to the end of the range, and the range contained characters with
100        more than one other case, caused incorrect behaviour when compiled in UTF
101        mode. In that example, the range a-j was left out of the class.
103    26. Fix JIT compilation of conditional blocks, which assertion
104        is converted to (*FAIL). E.g: /(?(?!))/.
106    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
107        discovered by the LLVM fuzzer.
109    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
110        when this assertion was used as a condition, for example (?(?!)a|b). In
111        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
112        error about an unsupported item.
114    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
115        possessification code could take exponential time to complete. A recursion
116        depth limit of 1000 has been imposed to limit the resources used by this
117        optimization.
119    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
120        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
121        because \S ensures they are all in the class. The code for doing this was
122        interacting badly with the code for computing the amount of space needed to
123        compile the pattern, leading to a buffer overflow. This bug was discovered
124        by the LLVM fuzzer.
126    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
127        other kinds of group caused stack overflow at compile time. This bug was
128        discovered by the LLVM fuzzer.
131    Version 8.36 26-September-2014
132    ------------------------------
134    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
135        -Wmissing-field-initializers and -Wunused-parameter.
137    2.  The tests for quantifiers being too big (greater than 65535) were being
138        applied after reading the number, and stupidly assuming that integer
139        overflow would give a negative number. The tests are now applied as the
140        numbers are read.
142    3.  Tidy code in pcre_exec.c where two branches that used to be different are
143        now the same.
145    4.  The JIT compiler did not generate match limit checks for certain
146        bracketed expressions with quantifiers. This may lead to exponential
147        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
148        issue should be resolved now.
150    5.  Fixed an issue, which occures when nested alternatives are optimized
151        with table jumps.
153    6.  Inserted two casts and changed some ints to size_t in the light of some
154        reported 64-bit compiler warnings (Bugzilla 1477).
156    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
157        an empty string, which sometimes were behaving incorrectly in the
158        interpreter (though correctly in the JIT matcher). This pcretest input is
159        an example:
161          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
164        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
165        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
166        for an empty string was breaking the inner loop and carrying on at a lower
167        level, when possessive repeated groups should always return to a higher
168        level as they have no backtrack points in them. The empty string test now
169        occurs at the outer level.
171    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
172        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
174    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
175        doesn't).
177    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
178        to hold a pattern to be incorrectly computed (too small) when there were
179        named back references to duplicated names. This could cause "internal
180        error: code overflow" or "double free or corruption" or other memory
181        handling errors.
183    11. When named subpatterns had the same prefixes, back references could be
184        confused. For example, in this pattern:
186          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
188        the reference to 'Name' was incorrectly treated as a reference to a
189        duplicate name.
191    12. A pattern such as /^s?c/mi8 where the optional character has more than
192        one "other case" was incorrectly compiled such that it would only try to
193        match starting at "c".
195    13. When a pattern starting with \s was studied, VT was not included in the
196        list of possible starting characters; this should have been part of the
197        8.34/18 patch.
199    14. If a character class started [\Qx]... where x is any character, the class
200        was incorrectly terminated at the ].
202    15. If a pattern that started with a caseless match for a character with more
203        than one "other case" was studied, PCRE did not set up the starting code
204        unit bit map for the list of possible characters. Now it does. This is an
205        optimization improvement, not a bug fix.
207    16. The Unicode data tables have been updated to Unicode 7.0.0.
209    17. Fixed a number of memory leaks in pcregrep.
211    18. Avoid a compiler warning (from some compilers) for a function call with
212        a cast that removes "const" from an lvalue by using an intermediate
213        variable (to which the compiler does not object).
215    19. Incorrect code was compiled if a group that contained an internal recursive
216        back reference was optional (had quantifier with a minimum of zero). This
217        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
218        caused segmentation faults because of stack overflows at compile time.
220    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
221        group that is quantified with an indefinite repeat, caused a compile-time
222        loop which used up all the system stack and provoked a segmentation fault.
223        This was not the same bug as 19 above.
225    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
226        Patch by Mike Frysinger.
229    Version 8.35 04-April-2014
230    --------------------------
232    1.  A new flag is set, when property checks are present in an XCLASS.
233        When this flag is not set, PCRE can perform certain optimizations
234        such as studying these XCLASS-es.
236    2.  The auto-possessification of character sets were improved: a normal
237        and an extended character set can be compared now. Furthermore
238        the JIT compiler optimizes more character set checks.
240    3.  Got rid of some compiler warnings for potentially uninitialized variables
241        that show up only when compiled with -O2.
243    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
244        of a match later then the end of the match. The pcretest program was not
245        handling the case sensibly - it was outputting from the start to the next
246        binary zero. It now reports this situation in a message, and outputs the
247        text from the end to the start.
249    5.  Fast forward search is improved in JIT. Instead of the first three
250        characters, any three characters with fixed position can be searched.
251        Search order: first, last, middle.
253    6.  Improve character range checks in JIT. Characters are read by an inprecise
254        function now, which returns with an unknown value if the character code is
255        above a certain threshold (e.g: 256). The only limitation is that the value
256        must be bigger than the threshold as well. This function is useful when
257        the characters above the threshold are handled in the same way.
259    7.  The macros whose names start with RAWUCHAR are placeholders for a future
260        mode in which only the bottom 21 bits of 32-bit data items are used. To
261        make this more memorable for those maintaining the code, the names have
262        been changed to start with UCHAR21, and an extensive comment has been added
263        to their definition.
265    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
266        to the export list in Makefile.am (they were accidentally omitted from the
267        8.34 tarball).
269    9.  The informational output from pcretest used the phrase "starting byte set"
270        which is inappropriate for the 16-bit and 32-bit libraries. As the output
271        for "first char" and "need char" really means "non-UTF-char", I've changed
272        "byte" to "char", and slightly reworded the output. The documentation about
273        these values has also been (I hope) clarified.
275    10. Another JIT related optimization: use table jumps for selecting the correct
276        backtracking path, when more than four alternatives are present inside a
277        bracket.
279    11. Empty match is not possible, when the minimum length is greater than zero,
280        and there is no \K in the pattern. JIT should avoid empty match checks in
281        such cases.
283    12. In a caseless character class with UCP support, when a character with more
284        than one alternative case was not the first character of a range, not all
285        the alternative cases were added to the class. For example, s and \x{17f}
286        are both alternative cases for S: the class [RST] was handled correctly,
287        but [R-T] was not.
289    13. The configure.ac file always checked for pthread support when JIT was
290        enabled. This is not used in Windows, so I have put this test inside a
291        check for the presence of windows.h (which was already tested for).
293    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
294        The algorithm provides a way to skip certain starting offsets, and usually
295        faster than linear prefix searches.
297    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
298        as for 'fr_FR' and 'french'. For some reason, however, it then used the
299        Windows-specific input and output files, which have 'french' screwed in.
300        So this could never have worked. One of the problems with locales is that
301        they aren't always the same. I have now updated RunTest so that it checks
302        the output of the locale test (test 3) against three different output
303        files, and it allows the test to pass if any one of them matches. With luck
304        this should make the test pass on some versions of Solaris where it was
305        failing. Because of the uncertainty, the script did not used to stop if
306        test 3 failed; it now does. If further versions of a French locale ever
307        come to light, they can now easily be added.
309    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
310        there was a message during ./configure, but it did not stop. This now
311        provokes an error. The invalid example in README has been corrected.
312        If a value less than the minimum is given, the minimum value has always
313        been used, but now a warning is given.
315    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
316        was a bug in the test system, which is now fixed. Also, the list of various
317        configurations that are tested for each release did not have one with both
318        16/32 bits and --enable-bar-anycrlf. It now does.
320    18. pcretest was missing "-C bsr" for displaying the \R default setting.
322    19. Little endian PowerPC systems are supported now by the JIT compiler.
324    20. The fast forward newline mechanism could enter to an infinite loop on
325        certain invalid UTF-8 input. Although we don't support these cases
326        this issue can be fixed by a performance optimization.
328    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
329        not take account if existing stack usage. There is now a new global
330        variable called pcre_stack_guard that can be set to point to an external
331        function to check stack availability. It is called at the start of
332        processing every parenthesized group.
334    22. A typo in the code meant that in ungreedy mode the max/min qualifier
335        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
336        not match "ab".
338    23. When UTF was disabled, the JIT program reported some incorrect compile
339        errors. These messages are silenced now.
341    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
342        compiler.
344    25. Change all the temporary files used in RunGrepTest to be different to those
345        used by RunTest so that the tests can be run simultaneously, for example by
346        "make -j check".
349    Version 8.34 15-December-2013
350  -----------------------------  -----------------------------
352    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
353        executable memory. Patch inspired by Carsten Klein.
355    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
356        this macro is never tested and has no effect, because the work to support
357        coverage involves only compiling and linking options and special targets in
358        the Makefile. The comment in config.h implied that defining the macro would
359        enable coverage support, which is totally false. There was also support for
360        setting this macro in the CMake files (my fault, I just copied it from
361        configure). SUPPORT_GCOV has now been removed.
363    3.  Make a small performance improvement in strlen16() and strlen32() in
364        pcretest.
366    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
367        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
368        these cases). There was also one in pcretest.c.
370    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
372    6.  In UTF mode, the code for checking whether a group could match an empty
373        string (which is used for indefinitely repeated groups to allow for
374        breaking an infinite loop) was broken when the group contained a repeated
375        negated single-character class with a character that occupied more than one
376        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
377        UTF-8 mode). The effect was undefined: the group might or might not be
378        deemed as matching an empty string, or the program might have crashed.
380    7.  The code for checking whether a group could match an empty string was not
381        recognizing that \h, \H, \v, \V, and \R must match a character.
383    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
384        an empty string. If it can, pcretest shows this in its information output.
386    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
387        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
388        matched by pcre_exec() without using JIT:
390        (a) If the rest of the pattern did not match after a maximal run of
391            grapheme clusters, the code for backing up to try with fewer of them
392            did not always back up over a full grapheme when characters that do not
393            have the modifier quality were involved, e.g. Hangul syllables.
395        (b) If the match point in a subject started with modifier character, and
396            there was no match, the code could incorrectly back up beyond the match
397            point, and potentially beyond the first character in the subject,
398            leading to a segfault or an incorrect match result.
400    10. A conditional group with an assertion condition could lead to PCRE
401        recording an incorrect first data item for a match if no other first data
402        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
403        first data item, and therefore matched "ca" after "c" instead of at the
404        start.
406    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
407        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
409    12. The source of pcregrep now includes z/OS-specific code so that it can be
410        compiled for z/OS as part of the special z/OS distribution.
412    13. Added the -T and -TM options to pcretest.
414    14. The code in pcre_compile.c for creating the table of named capturing groups
415        has been refactored. Instead of creating the table dynamically during the
416        actual compiling pass, the information is remembered during the pre-compile
417        pass (on the stack unless there are more than 20 named groups, in which
418        case malloc() is used) and the whole table is created before the actual
419        compile happens. This has simplified the code (it is now nearly 150 lines
420        shorter) and prepared the way for better handling of references to groups
421        with duplicate names.
423    15. A back reference to a named subpattern when there is more than one of the
424        same name now checks them in the order in which they appear in the pattern.
425        The first one that is set is used for the reference. Previously only the
426        first one was inspected. This change makes PCRE more compatible with Perl.
428    16. Unicode character properties were updated from Unicode 6.3.0.
430    17. The compile-time code for auto-possessification has been refactored, based
431        on a patch by Zoltan Herczeg. It now happens after instead of during
432        compilation. The code is cleaner, and more cases are handled. The option
433        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
434        options in pcretest are provided to set it. It can also be set by
435        (*NO_AUTO_POSSESS) at the start of a pattern.
437    18. The character VT has been added to the default ("C" locale) set of
438        characters that match \s and are generally treated as white space,
439        following this same change in Perl 5.18. There is now no difference between
440        "Perl space" and "POSIX space". Whether VT is treated as white space in
441        other locales depends on the locale.
443    19. The code for checking named groups as conditions, either for being set or
444        for being recursed, has been refactored (this is related to 14 and 15
445        above). Processing unduplicated named groups should now be as fast at
446        numerical groups, and processing duplicated groups should be faster than
447        before.
449    20. Two patches to the CMake build system, by Alexander Barkov:
451          (1) Replace the "source" command by "." in CMakeLists.txt because
452              "source" is a bash-ism.
454          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
455              without these the CMake build does not work on Solaris.
457    21. Perl has changed its handling of \8 and \9. If there is no previously
458        encountered capturing group of those numbers, they are treated as the
459        literal characters 8 and 9 instead of a binary zero followed by the
460        literals. PCRE now does the same.
462    22. Following Perl, added \o{} to specify codepoints in octal, making it
463        possible to specify values greater than 0777 and also making them
464        unambiguous.
466    23. Perl now gives an error for missing closing braces after \x{... instead of
467        treating the string as literal. PCRE now does the same.
469    24. RunTest used to grumble if an inappropriate test was selected explicitly,
470        but just skip it when running all tests. This make it awkward to run ranges
471        of tests when one of them was inappropriate. Now it just skips any
472        inappropriate tests, as it always did when running all tests.
474    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
475        character types such as \d or \w, too many callouts were inserted, and the
476        data that they returned was rubbish.
478    26. In UCP mode, \s was not matching two of the characters that Perl matches,
479        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
480        were matched by \h. The code has now been refactored so that the lists of
481        the horizontal and vertical whitespace characters used for \h and \v (which
482        are defined only in one place) are now also used for \s.
484    27. Add JIT support for the 64 bit TileGX architecture.
485        Patch by Jiong Wang (Tilera Corporation).
487    28. Possessive quantifiers for classes (both explicit and automatically
488        generated) now use special opcodes instead of wrapping in ONCE brackets.
490    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
491        (because it's meaningless), this was not happening when PCRE_CASELESS was
492        set. Not wrong, but inefficient.
494    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
495        properties for \w, \d, etc) is present in a test regex. Otherwise if the
496        test contains no characters greater than 255, Perl doesn't realise it
497        should be using Unicode semantics.
499    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
500        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
501        does in Unicode mode.
503    32. Added the "forbid" facility to pcretest so that putting tests into the
504        wrong test files can sometimes be quickly detected.
506    33. There is now a limit (default 250) on the depth of nesting of parentheses.
507        This limit is imposed to control the amount of system stack used at compile
508        time. It can be changed at build time by --with-parens-nest-limit=xxx or
509        the equivalent in CMake.
511    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
512        errors. Perl warns for these when in warning mode, but PCRE has no facility
513        for giving warnings.
515    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
516        However, this was not working for (?!) because it is optimized to (*FAIL),
517        for which PCRE does not allow quantifiers. The optimization is now disabled
518        when a quantifier follows (?!). I can't see any use for this, but it makes
519        things uniform.
521    36. Perl no longer allows group names to start with digits, so I have made this
522        change also in PCRE. It simplifies the code a bit.
524    37. In extended mode, Perl ignores spaces before a + that indicates a
525        possessive quantifier. PCRE allowed a space before the quantifier, but not
526        before the possessive +. It now does.
528    38. The use of \K (reset reported match start) within a repeated possessive
529        group such as (a\Kb)*+ was not working.
531    40. Document that the same character tables must be used at compile time and
532        run time, and that the facility to pass tables to pcre_exec() and
533        pcre_dfa_exec() is for use only with saved/restored patterns.
535    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
536        features for Builds with MSVC:
538        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
539           builds). The .rc files can be used to set FileDescription and many other
540           attributes.
542        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
543           This allows higher-level build scripts which want .pdb files to avoid
544           hard-coding the exact files needed."
546    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
547        mean "start of word" and "end of word", respectively, as a transition aid.
549    43. A minimizing repeat of a class containing codepoints greater than 255 in
550        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
551        compiled to use the heap for recursion.
553    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
554        is configured.
557    Version 8.33 28-May-2013
558    ------------------------
560    1.  Added 'U' to some constants that are compared to unsigned integers, to
561        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
562        variables that are added to signed variables, to ensure the result is
563        signed and can be negated.
565    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
566        CMake config files.
568    3.  Revise the creation of config.h.generic so that all boolean macros are
569        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
570        overriding via -D on the command line possible.
572    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
573        to unsigned int is reported to make a quite noticeable speed difference in
574        a specific Windows environment. Testing on Linux did also appear to show
575        some benefit (and it is clearly not harmful). Also fixed the definition of
576        Xop which should be unsigned.
578    5.  Related to (4), changing the definition of the intermediate variable cc
579        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
580        improvements.
582    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
583        unnecessary spaces.
585    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
586        and later.
588    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
590    9.  Optimizing fast_forward_start_bits in JIT.
592    10. Adding support for callouts in JIT, and fixing some issues revealed
593        during this work. Namely:
595        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
597        (b) Minimum length was not checked before the matching is started.
599    11. The value of capture_last that is passed to callouts was incorrect in some
600        cases when there was a capture on one path that was subsequently abandoned
601        after a backtrack. Also, the capture_last value is now reset after a
602        recursion, since all captures are also reset in this case.
604    12. The interpreter no longer returns the "too many substrings" error in the
605        case when an overflowing capture is in a branch that is subsequently
606        abandoned after a backtrack.
608    13. In the pathological case when an offset vector of size 2 is used, pcretest
609        now prints out the matched string after a yield of 0 or 1.
611    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
612        Only supported by the JIT compiler at the moment.
614    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
616    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
617        offset of the starting point of the matching process, provided the offsets
618        vector is large enough.
620    17. The \A escape now records a lookbehind value of 1, though its execution
621        does not actually inspect the previous character. This is to ensure that,
622        in partial multi-segment matching, at least one character from the old
623        segment is retained when a new segment is processed. Otherwise, if there
624        are no lookbehinds in the pattern, \A might match incorrectly at the start
625        of a new segment.
627    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
629    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
630        gives some modest performance improvement in 8-bit mode.
632    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
633        be expressed in certain programming languages using Universal Character
634        Names.
636    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
637        which points out that "non characters" are not "characters that may not
638        appear in Unicode strings" but rather "characters that are reserved for
639        internal use and have only local meaning".
641    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
642        there was a conditional group that depended on an assertion, if the
643        assertion was false, the callout that immediately followed the alternation
644        in the condition was skipped when pcre_exec() was used for matching.
646    23. Allow an explicit callout to be inserted before an assertion that is the
647        condition for a conditional group, for compatibility with automatic
648        callouts, which always insert a callout at this point.
650    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
651        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
653    25. (*PRUNE) is now supported by the JIT compiler.
655    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
657    27. Fix the case where there are two or more SKIPs with arguments that may be
658        ignored.
660    28. (*SKIP) is now supported by the JIT compiler.
662    29. (*THEN) is now supported by the JIT compiler.
664    30. Update RunTest with additional test selector options.
666    31. The way PCRE handles backtracking verbs has been changed in two ways.
668        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
669        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
670        backtracking. In some cases this makes it more Perl-compatible, but Perl's
671        rather obscure rules do not always do the same thing.
673        (2) Previously, backtracking verbs were confined within assertions. This is
674        no longer the case for positive assertions, except for (*ACCEPT). Again,
675        this sometimes improves Perl compatibility, and sometimes does not.
677    32. A number of tests that were in test 2 because Perl did things differently
678        have been moved to test 1, because either Perl or PCRE has changed, and
679        these tests are now compatible.
681    32. Backtracking control verbs are now handled in the same way in JIT and
682        interpreter.
684    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
685        contained a forward subroutine reference caused a compile error.
687    34. Auto-detect and optimize limited repetitions in JIT.
689    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
690        blocking (*UTF) etc.
692    36. In the interpreter, maximizing pattern repetitions for characters and
693        character types now use tail recursion, which reduces stack usage.
695    37. The value of the max lookbehind was not correctly preserved if a compiled
696        and saved regex was reloaded on a host of different endianness.
698    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
699        of the compiled pattern block, expand the flags field from 16 to 32 bits
700        because it was almost full.
702    39. Try madvise first before posix_madvise.
704    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
705        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
706        original change locked out all matches of empty strings. This has been
707        changed so that one match of an empty string per line is recognized.
708        Subsequent searches on the same line (for colouring or for --only-matching,
709        for example) do not recognize empty strings.
711    41. Applied a user patch to fix a number of spelling mistakes in comments.
713    42. Data lines longer than 65536 caused pcretest to crash.
715    43. Clarified the data type for length and startoffset arguments for pcre_exec
716        and pcre_dfa_exec in the function-specific man pages, where they were
717        explicitly stated to be in bytes, never having been updated. I also added
718        some clarification to the pcreapi man page.
720    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
721        a segmentation fault.
724    Version 8.32 30-November-2012
725    -----------------------------
727    1.  Improved JIT compiler optimizations for first character search and single
728        character iterators.
730    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
731        Patch by Daniel Richard G.
733    3.  Single character iterator optimizations in the JIT compiler.
735    4.  Improved JIT compiler optimizations for character ranges.
737    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
738        Reported by Giuseppe D'Angelo.
740    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
741        of a line, was being set incorrectly in cases where .* appeared inside
742        atomic brackets at the start of a pattern, or where there was a subsequent
743        *PRUNE or *SKIP.
745    7.  Improved instruction cache flush for POWER/PowerPC.
746        Patch by Daniel Richard G.
748    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
749        grep:
751        (a) There is now no limit to the number of patterns to be matched.
753        (b) An error is given if a pattern is too long.
755        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
756            are now supported.
758        (d) --exclude-from and --include-from (multiple use) have been added.
760        (e) Exclusions and inclusions now apply to all files and directories, not
761            just to those obtained from scanning a directory recursively.
763        (f) Multiple uses of -f and --file-list are now supported.
765        (g) In a Windows environment, the default for -d has been changed from
766            "read" (the GNU grep default) to "skip", because otherwise the presence
767            of a directory in the file list provokes an error.
769        (h) The documentation has been revised and clarified in places.
771    9.  Improve the matching speed of capturing brackets.
773    10. Changed the meaning of \X so that it now matches a Unicode extended
774        grapheme cluster.
776    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
777        out POSIX threads when JIT support is configured.
779    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
781    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
782        structure could go wrong in environments where size_t is not the same size
783        as int.
785    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
786        set.
788    15. The EBCDIC support had decayed; later updates to the code had included
789        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
790        general tidy up of EBCDIC-related issues, and the documentation was also
791        not quite right. There is now a test that can be run on ASCII systems to
792        check some of the EBCDIC-related things (but is it not a full test).
794    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
795        in a small tidy to the code.
797    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
799    18. If the --only-matching (-o) option in pcregrep is specified multiple
800        times, each one causes appropriate output. For example, -o1 -o2 outputs the
801        substrings matched by the 1st and 2nd capturing parentheses. A separating
802        string can be specified by --om-separator (default empty).
804    19. Improving the first n character searches.
806    20. Turn case lists for horizontal and vertical white space into macros so that
807        they are defined only once.
809    21. This set of changes together give more compatible Unicode case-folding
810        behaviour for characters that have more than one other case when UCP
811        support is available.
813        (a) The Unicode property table now has offsets into a new table of sets of
814            three or more characters that are case-equivalent. The MultiStage2.py
815            script that generates these tables (the pcre_ucd.c file) now scans
816            CaseFolding.txt instead of UnicodeData.txt for character case
817            information.
819        (b) The code for adding characters or ranges of characters to a character
820            class has been abstracted into a generalized function that also handles
821            case-independence. In UTF-mode with UCP support, this uses the new data
822            to handle characters with more than one other case.
824        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
825            whose other case is greater than 256 are now correctly matched
826            caselessly. Previously, the high codepoint matched the low one, but not
827            vice versa.
829        (d) The processing of \h, \H, \v, and \ in character classes now makes use
830            of the new class addition function, using character lists defined as
831            macros alongside the case definitions of 20 above.
833        (e) Caseless back references now work with characters that have more than
834            one other case.
836        (f) General caseless matching of characters with more than one other case
837            is supported.
839    22. Unicode character properties were updated from Unicode 6.2.0
841    23. Improved CMake support under Windows. Patch by Daniel Richard G.
843    24. Add support for 32-bit character strings, and UTF-32
845    25. Major JIT compiler update (code refactoring and bugfixing).
846        Experimental Sparc 32 support is added.
848    26. Applied a modified version of Daniel Richard G's patch to create
849        pcre.h.generic and config.h.generic by "make" instead of in the
850        PrepareRelease script.
852    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
853        pcre_compile.c when checking for a zero character.
855    28. Introducing a native interface for JIT. Through this interface, the compiled
856        machine code can be directly executed. The purpose of this interface is to
857        provide fast pattern matching, so several sanity checks are not performed.
858        However, feature tests are still performed. The new interface provides
859        1.4x speedup compared to the old one.
861    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
862        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
863        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
865    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
866        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
867        the "old" RFC 2279). Instead, it ended up passing a negative length to
868        pcre_exec().
870    31. Add support for GCC's visibility feature to hide internal functions.
872    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
873        "unknown -C option" after outputting 0 or 1.
875    33. There is now support for generating a code coverage report for the test
876        suite in environments where gcc is the compiler and lcov is installed. This
877        is mainly for the benefit of the developers.
879    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
880        unaddressable using valgrind annotations, allowing valgrind to detect
881        invalid memory accesses. This is mainly for the benefit of the developers.
883    25. (*UTF) can now be used to start a pattern in any of the three libraries.
885    26. Give configure error if --enable-cpp but no C++ compiler found.
888    Version 8.31 06-July-2012
889    -------------------------
891  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
893  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
895  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
896      to unsigned type, result still unsigned" that was given by an MS compiler      to unsigned type, result still unsigned" that was given by an MS compiler
897      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
899  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
# Line 18  Version 8.31 Line 902  Version 8.31
902      of more than one character:      of more than one character:
904      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
905          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
906          references.          references.
908      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
909          subject.          subject.
911      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
912          characters at the end of the subject.          characters at the end of the subject.
914      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
# Line 33  Version 8.31 Line 917  Version 8.31
917      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
918          a partial match for a CR character at the end of the subject string.          a partial match for a CR character at the end of the subject string.
920  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
921      running pcretest, the text "(JIT)" added to the output whenever JIT is      running pcretest, the text "(JIT)" added to the output whenever JIT is
922      actually used to run the match.      actually used to run the match.
924  7.  Individual JIT compile options can be set in pcretest by following -s+[+]  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
925      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
927  8.  OP_NOT now supports any UTF character not just single-byte ones.  8.  OP_NOT now supports any UTF character not just single-byte ones.
# Line 46  Version 8.31 Line 930  Version 8.31
931  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
932      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
936  12. Applied a (slightly modified) user-supplied patch that improves performance  12. Applied a (slightly modified) user-supplied patch that improves performance
937      when the heap is used for recursion (compiled with --disable-stack-for-      when the heap is used for recursion (compiled with --disable-stack-for-
938      recursion). Instead of malloc and free for each heap frame each time a      recursion). Instead of malloc and free for each heap frame each time a
939      logical recursion happens, frames are retained on a chain and re-used where      logical recursion happens, frames are retained on a chain and re-used where
940      possible. This sometimes gives as much as 30% improvement.      possible. This sometimes gives as much as 30% improvement.
942  13. (*COMMIT) is now correctly confined to within a recursive subpattern call.  13. As documented, (*COMMIT) is now confined to within a recursive subpattern
943        call.
945    14. As documented, (*COMMIT) is now confined to within a positive assertion.
947    15. It is now possible to link pcretest with libedit as an alternative to
948        libreadline.
950    16. (*COMMIT) control verb is now supported by the JIT compiler.
952    17. The Unicode data tables have been updated to Unicode 6.1.0.
954    18. Added --file-list option to pcregrep.
956    19. Added binary file support to pcregrep, including the -a, --binary-files,
957        -I, and --text options.
959    20. The madvise function is renamed for posix_madvise for QNX compatibility
960        reasons. Fixed by Giuseppe D'Angelo.
962    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
964    22. Changed the option for creating symbolic links for 16-bit man pages from
965        -s to -sf so that re-installing does not cause issues.
967    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
969    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
970        matches in certain environments (the workspace was not being correctly
971        retained). Also added to pcre_dfa_exec() a simple plausibility check on
972        some of the workspace data at the beginning of a restart.
974    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
975        was not doing so when it should - probably a typo introduced by SVN 528
976        (change 8.10/14).
978    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
979        \w+ when the character tables indicated that \x{c4} was a word character.
980        There were several related cases, all because the tests for doing a table
981        lookup were testing for characters less than 127 instead of 255.
983    27. If a pattern contains capturing parentheses that are not used in a match,
984        their slots in the ovector are set to -1. For those that are higher than
985        any matched groups, this happens at the end of processing. In the case when
986        there were back references that the ovector was too small to contain
987        (causing temporary malloc'd memory to be used during matching), and the
988        highest capturing number was not used, memory off the end of the ovector
989        was incorrectly being set to -1. (It was using the size of the temporary
990        memory instead of the true size.)
992    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
993        ovector size, it uses memory at the end of the block that it has got.
995    29. Check for an overlong MARK name and give an error at compile time. The
996        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
998    30. JIT compiler update.
1000    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
1001        Rill for the patch.
1003    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
1005    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
1007    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
1008        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
1009        was enabled.
1011    35. Improve JIT code generation for greedy plus quantifier.
1013    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
1014        1 to "aa" instead of to an empty string. The bug affected repeated groups
1015        that could potentially match an empty string.
1017    37. Optimizing single character iterators in JIT.
1019    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
1020        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
1021        codepoints that are too big for the mode are faulted, and in a UTF mode,
1022        disallowed codepoints are also faulted.
1024    39. If PCRE was compiled with UTF support, in three places in the DFA
1025        matcher there was code that should only have been obeyed in UTF mode, but
1026        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
1027        processing when bytes with values greater than 127 were present. In 16-bit
1028        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
1029        both cases the values are those that cannot be the first data item in a UTF
1030        character. The three items that might have provoked this were recursions,
1031        possessively repeated groups, and atomic groups.
1033    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
1034        and pcregrep, because some OS require shared objects to be explicitly
1035        passed to ld, causing the link step to fail if they are not.
1037    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
1038        mode, patterns that started with \h* or \R* might be incorrectly matched.
1041  Version 8.30 04-February-2012  Version 8.30 04-February-2012
# Line 1248  Version 7.9 11-Apr-09 Line 2228  Version 7.9 11-Apr-09
2228  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
2229      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
2230      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2231      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2232        8.33.]
2234  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
2235      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1491  Version 7.7 07-May-08 Line 2472  Version 7.7 07-May-08
2472      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2473      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2474      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2475      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2476      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2477      was subsequently set up correctly.)      was subsequently set up correctly.)

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

  ViewVC Help
Powered by ViewVC 1.1.5