ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 942 by ph10, Tue Feb 28 14:50:31 2012 UTC revision 1534 by ph10, Tue Mar 24 10:33:21 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.
115    Version 8.36 26-September-2014
116    ------------------------------
118    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
119        -Wmissing-field-initializers and -Wunused-parameter.
121    2.  The tests for quantifiers being too big (greater than 65535) were being
122        applied after reading the number, and stupidly assuming that integer
123        overflow would give a negative number. The tests are now applied as the
124        numbers are read.
126    3.  Tidy code in pcre_exec.c where two branches that used to be different are
127        now the same.
129    4.  The JIT compiler did not generate match limit checks for certain
130        bracketed expressions with quantifiers. This may lead to exponential
131        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
132        issue should be resolved now.
134    5.  Fixed an issue, which occures when nested alternatives are optimized
135        with table jumps.
137    6.  Inserted two casts and changed some ints to size_t in the light of some
138        reported 64-bit compiler warnings (Bugzilla 1477).
140    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
141        an empty string, which sometimes were behaving incorrectly in the
142        interpreter (though correctly in the JIT matcher). This pcretest input is
143        an example:
145          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
148        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
149        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
150        for an empty string was breaking the inner loop and carrying on at a lower
151        level, when possessive repeated groups should always return to a higher
152        level as they have no backtrack points in them. The empty string test now
153        occurs at the outer level.
155    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
156        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
158    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
159        doesn't).
161    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
162        to hold a pattern to be incorrectly computed (too small) when there were
163        named back references to duplicated names. This could cause "internal
164        error: code overflow" or "double free or corruption" or other memory
165        handling errors.
167    11. When named subpatterns had the same prefixes, back references could be
168        confused. For example, in this pattern:
170          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
172        the reference to 'Name' was incorrectly treated as a reference to a
173        duplicate name.
175    12. A pattern such as /^s?c/mi8 where the optional character has more than
176        one "other case" was incorrectly compiled such that it would only try to
177        match starting at "c".
179    13. When a pattern starting with \s was studied, VT was not included in the
180        list of possible starting characters; this should have been part of the
181        8.34/18 patch.
183    14. If a character class started [\Qx]... where x is any character, the class
184        was incorrectly terminated at the ].
186    15. If a pattern that started with a caseless match for a character with more
187        than one "other case" was studied, PCRE did not set up the starting code
188        unit bit map for the list of possible characters. Now it does. This is an
189        optimization improvement, not a bug fix.
191    16. The Unicode data tables have been updated to Unicode 7.0.0.
193    17. Fixed a number of memory leaks in pcregrep.
195    18. Avoid a compiler warning (from some compilers) for a function call with
196        a cast that removes "const" from an lvalue by using an intermediate
197        variable (to which the compiler does not object).
199    19. Incorrect code was compiled if a group that contained an internal recursive
200        back reference was optional (had quantifier with a minimum of zero). This
201        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
202        caused segmentation faults because of stack overflows at compile time.
204    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
205        group that is quantified with an indefinite repeat, caused a compile-time
206        loop which used up all the system stack and provoked a segmentation fault.
207        This was not the same bug as 19 above.
209    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
210        Patch by Mike Frysinger.
213    Version 8.35 04-April-2014
214    --------------------------
216    1.  A new flag is set, when property checks are present in an XCLASS.
217        When this flag is not set, PCRE can perform certain optimizations
218        such as studying these XCLASS-es.
220    2.  The auto-possessification of character sets were improved: a normal
221        and an extended character set can be compared now. Furthermore
222        the JIT compiler optimizes more character set checks.
224    3.  Got rid of some compiler warnings for potentially uninitialized variables
225        that show up only when compiled with -O2.
227    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
228        of a match later then the end of the match. The pcretest program was not
229        handling the case sensibly - it was outputting from the start to the next
230        binary zero. It now reports this situation in a message, and outputs the
231        text from the end to the start.
233    5.  Fast forward search is improved in JIT. Instead of the first three
234        characters, any three characters with fixed position can be searched.
235        Search order: first, last, middle.
237    6.  Improve character range checks in JIT. Characters are read by an inprecise
238        function now, which returns with an unknown value if the character code is
239        above a certain threshold (e.g: 256). The only limitation is that the value
240        must be bigger than the threshold as well. This function is useful when
241        the characters above the threshold are handled in the same way.
243    7.  The macros whose names start with RAWUCHAR are placeholders for a future
244        mode in which only the bottom 21 bits of 32-bit data items are used. To
245        make this more memorable for those maintaining the code, the names have
246        been changed to start with UCHAR21, and an extensive comment has been added
247        to their definition.
249    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
250        to the export list in Makefile.am (they were accidentally omitted from the
251        8.34 tarball).
253    9.  The informational output from pcretest used the phrase "starting byte set"
254        which is inappropriate for the 16-bit and 32-bit libraries. As the output
255        for "first char" and "need char" really means "non-UTF-char", I've changed
256        "byte" to "char", and slightly reworded the output. The documentation about
257        these values has also been (I hope) clarified.
259    10. Another JIT related optimization: use table jumps for selecting the correct
260        backtracking path, when more than four alternatives are present inside a
261        bracket.
263    11. Empty match is not possible, when the minimum length is greater than zero,
264        and there is no \K in the pattern. JIT should avoid empty match checks in
265        such cases.
267    12. In a caseless character class with UCP support, when a character with more
268        than one alternative case was not the first character of a range, not all
269        the alternative cases were added to the class. For example, s and \x{17f}
270        are both alternative cases for S: the class [RST] was handled correctly,
271        but [R-T] was not.
273    13. The configure.ac file always checked for pthread support when JIT was
274        enabled. This is not used in Windows, so I have put this test inside a
275        check for the presence of windows.h (which was already tested for).
277    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
278        The algorithm provides a way to skip certain starting offsets, and usually
279        faster than linear prefix searches.
281    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
282        as for 'fr_FR' and 'french'. For some reason, however, it then used the
283        Windows-specific input and output files, which have 'french' screwed in.
284        So this could never have worked. One of the problems with locales is that
285        they aren't always the same. I have now updated RunTest so that it checks
286        the output of the locale test (test 3) against three different output
287        files, and it allows the test to pass if any one of them matches. With luck
288        this should make the test pass on some versions of Solaris where it was
289        failing. Because of the uncertainty, the script did not used to stop if
290        test 3 failed; it now does. If further versions of a French locale ever
291        come to light, they can now easily be added.
293    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
294        there was a message during ./configure, but it did not stop. This now
295        provokes an error. The invalid example in README has been corrected.
296        If a value less than the minimum is given, the minimum value has always
297        been used, but now a warning is given.
299    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
300        was a bug in the test system, which is now fixed. Also, the list of various
301        configurations that are tested for each release did not have one with both
302        16/32 bits and --enable-bar-anycrlf. It now does.
304    18. pcretest was missing "-C bsr" for displaying the \R default setting.
306    19. Little endian PowerPC systems are supported now by the JIT compiler.
308    20. The fast forward newline mechanism could enter to an infinite loop on
309        certain invalid UTF-8 input. Although we don't support these cases
310        this issue can be fixed by a performance optimization.
312    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
313        not take account if existing stack usage. There is now a new global
314        variable called pcre_stack_guard that can be set to point to an external
315        function to check stack availability. It is called at the start of
316        processing every parenthesized group.
318    22. A typo in the code meant that in ungreedy mode the max/min qualifier
319        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
320        not match "ab".
322    23. When UTF was disabled, the JIT program reported some incorrect compile
323        errors. These messages are silenced now.
325    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
326        compiler.
328    25. Change all the temporary files used in RunGrepTest to be different to those
329        used by RunTest so that the tests can be run simultaneously, for example by
330        "make -j check".
333    Version 8.34 15-December-2013
334    -----------------------------
336    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
337        executable memory. Patch inspired by Carsten Klein.
339    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
340        this macro is never tested and has no effect, because the work to support
341        coverage involves only compiling and linking options and special targets in
342        the Makefile. The comment in config.h implied that defining the macro would
343        enable coverage support, which is totally false. There was also support for
344        setting this macro in the CMake files (my fault, I just copied it from
345        configure). SUPPORT_GCOV has now been removed.
347    3.  Make a small performance improvement in strlen16() and strlen32() in
348        pcretest.
350    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
351        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
352        these cases). There was also one in pcretest.c.
354    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
356    6.  In UTF mode, the code for checking whether a group could match an empty
357        string (which is used for indefinitely repeated groups to allow for
358        breaking an infinite loop) was broken when the group contained a repeated
359        negated single-character class with a character that occupied more than one
360        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
361        UTF-8 mode). The effect was undefined: the group might or might not be
362        deemed as matching an empty string, or the program might have crashed.
364    7.  The code for checking whether a group could match an empty string was not
365        recognizing that \h, \H, \v, \V, and \R must match a character.
367    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
368        an empty string. If it can, pcretest shows this in its information output.
370    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
371        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
372        matched by pcre_exec() without using JIT:
374        (a) If the rest of the pattern did not match after a maximal run of
375            grapheme clusters, the code for backing up to try with fewer of them
376            did not always back up over a full grapheme when characters that do not
377            have the modifier quality were involved, e.g. Hangul syllables.
379        (b) If the match point in a subject started with modifier character, and
380            there was no match, the code could incorrectly back up beyond the match
381            point, and potentially beyond the first character in the subject,
382            leading to a segfault or an incorrect match result.
384    10. A conditional group with an assertion condition could lead to PCRE
385        recording an incorrect first data item for a match if no other first data
386        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
387        first data item, and therefore matched "ca" after "c" instead of at the
388        start.
390    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
391        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
393    12. The source of pcregrep now includes z/OS-specific code so that it can be
394        compiled for z/OS as part of the special z/OS distribution.
396    13. Added the -T and -TM options to pcretest.
398    14. The code in pcre_compile.c for creating the table of named capturing groups
399        has been refactored. Instead of creating the table dynamically during the
400        actual compiling pass, the information is remembered during the pre-compile
401        pass (on the stack unless there are more than 20 named groups, in which
402        case malloc() is used) and the whole table is created before the actual
403        compile happens. This has simplified the code (it is now nearly 150 lines
404        shorter) and prepared the way for better handling of references to groups
405        with duplicate names.
407    15. A back reference to a named subpattern when there is more than one of the
408        same name now checks them in the order in which they appear in the pattern.
409        The first one that is set is used for the reference. Previously only the
410        first one was inspected. This change makes PCRE more compatible with Perl.
412    16. Unicode character properties were updated from Unicode 6.3.0.
414    17. The compile-time code for auto-possessification has been refactored, based
415        on a patch by Zoltan Herczeg. It now happens after instead of during
416        compilation. The code is cleaner, and more cases are handled. The option
417        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
418        options in pcretest are provided to set it. It can also be set by
419        (*NO_AUTO_POSSESS) at the start of a pattern.
421    18. The character VT has been added to the default ("C" locale) set of
422        characters that match \s and are generally treated as white space,
423        following this same change in Perl 5.18. There is now no difference between
424        "Perl space" and "POSIX space". Whether VT is treated as white space in
425        other locales depends on the locale.
427    19. The code for checking named groups as conditions, either for being set or
428        for being recursed, has been refactored (this is related to 14 and 15
429        above). Processing unduplicated named groups should now be as fast at
430        numerical groups, and processing duplicated groups should be faster than
431        before.
433    20. Two patches to the CMake build system, by Alexander Barkov:
435          (1) Replace the "source" command by "." in CMakeLists.txt because
436              "source" is a bash-ism.
438          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
439              without these the CMake build does not work on Solaris.
441    21. Perl has changed its handling of \8 and \9. If there is no previously
442        encountered capturing group of those numbers, they are treated as the
443        literal characters 8 and 9 instead of a binary zero followed by the
444        literals. PCRE now does the same.
446    22. Following Perl, added \o{} to specify codepoints in octal, making it
447        possible to specify values greater than 0777 and also making them
448        unambiguous.
450    23. Perl now gives an error for missing closing braces after \x{... instead of
451        treating the string as literal. PCRE now does the same.
453    24. RunTest used to grumble if an inappropriate test was selected explicitly,
454        but just skip it when running all tests. This make it awkward to run ranges
455        of tests when one of them was inappropriate. Now it just skips any
456        inappropriate tests, as it always did when running all tests.
458    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
459        character types such as \d or \w, too many callouts were inserted, and the
460        data that they returned was rubbish.
462    26. In UCP mode, \s was not matching two of the characters that Perl matches,
463        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
464        were matched by \h. The code has now been refactored so that the lists of
465        the horizontal and vertical whitespace characters used for \h and \v (which
466        are defined only in one place) are now also used for \s.
468    27. Add JIT support for the 64 bit TileGX architecture.
469        Patch by Jiong Wang (Tilera Corporation).
471    28. Possessive quantifiers for classes (both explicit and automatically
472        generated) now use special opcodes instead of wrapping in ONCE brackets.
474    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
475        (because it's meaningless), this was not happening when PCRE_CASELESS was
476        set. Not wrong, but inefficient.
478    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
479        properties for \w, \d, etc) is present in a test regex. Otherwise if the
480        test contains no characters greater than 255, Perl doesn't realise it
481        should be using Unicode semantics.
483    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
484        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
485        does in Unicode mode.
487    32. Added the "forbid" facility to pcretest so that putting tests into the
488        wrong test files can sometimes be quickly detected.
490    33. There is now a limit (default 250) on the depth of nesting of parentheses.
491        This limit is imposed to control the amount of system stack used at compile
492        time. It can be changed at build time by --with-parens-nest-limit=xxx or
493        the equivalent in CMake.
495    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
496        errors. Perl warns for these when in warning mode, but PCRE has no facility
497        for giving warnings.
499    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
500        However, this was not working for (?!) because it is optimized to (*FAIL),
501        for which PCRE does not allow quantifiers. The optimization is now disabled
502        when a quantifier follows (?!). I can't see any use for this, but it makes
503        things uniform.
505    36. Perl no longer allows group names to start with digits, so I have made this
506        change also in PCRE. It simplifies the code a bit.
508    37. In extended mode, Perl ignores spaces before a + that indicates a
509        possessive quantifier. PCRE allowed a space before the quantifier, but not
510        before the possessive +. It now does.
512    38. The use of \K (reset reported match start) within a repeated possessive
513        group such as (a\Kb)*+ was not working.
515    40. Document that the same character tables must be used at compile time and
516        run time, and that the facility to pass tables to pcre_exec() and
517        pcre_dfa_exec() is for use only with saved/restored patterns.
519    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
520        features for Builds with MSVC:
522        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
523           builds). The .rc files can be used to set FileDescription and many other
524           attributes.
526        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
527           This allows higher-level build scripts which want .pdb files to avoid
528           hard-coding the exact files needed."
530    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
531        mean "start of word" and "end of word", respectively, as a transition aid.
533    43. A minimizing repeat of a class containing codepoints greater than 255 in
534        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
535        compiled to use the heap for recursion.
537    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
538        is configured.
541    Version 8.33 28-May-2013
542    ------------------------
544    1.  Added 'U' to some constants that are compared to unsigned integers, to
545        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
546        variables that are added to signed variables, to ensure the result is
547        signed and can be negated.
549    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
550        CMake config files.
552    3.  Revise the creation of config.h.generic so that all boolean macros are
553        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
554        overriding via -D on the command line possible.
556    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
557        to unsigned int is reported to make a quite noticeable speed difference in
558        a specific Windows environment. Testing on Linux did also appear to show
559        some benefit (and it is clearly not harmful). Also fixed the definition of
560        Xop which should be unsigned.
562    5.  Related to (4), changing the definition of the intermediate variable cc
563        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
564        improvements.
566    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
567        unnecessary spaces.
569    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
570        and later.
572    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
574    9.  Optimizing fast_forward_start_bits in JIT.
576    10. Adding support for callouts in JIT, and fixing some issues revealed
577        during this work. Namely:
579        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
581        (b) Minimum length was not checked before the matching is started.
583    11. The value of capture_last that is passed to callouts was incorrect in some
584        cases when there was a capture on one path that was subsequently abandoned
585        after a backtrack. Also, the capture_last value is now reset after a
586        recursion, since all captures are also reset in this case.
588    12. The interpreter no longer returns the "too many substrings" error in the
589        case when an overflowing capture is in a branch that is subsequently
590        abandoned after a backtrack.
592    13. In the pathological case when an offset vector of size 2 is used, pcretest
593        now prints out the matched string after a yield of 0 or 1.
595    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
596        Only supported by the JIT compiler at the moment.
598    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
600    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
601        offset of the starting point of the matching process, provided the offsets
602        vector is large enough.
604    17. The \A escape now records a lookbehind value of 1, though its execution
605        does not actually inspect the previous character. This is to ensure that,
606        in partial multi-segment matching, at least one character from the old
607        segment is retained when a new segment is processed. Otherwise, if there
608        are no lookbehinds in the pattern, \A might match incorrectly at the start
609        of a new segment.
611    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
613    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
614        gives some modest performance improvement in 8-bit mode.
616    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
617        be expressed in certain programming languages using Universal Character
618        Names.
620    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
621        which points out that "non characters" are not "characters that may not
622        appear in Unicode strings" but rather "characters that are reserved for
623        internal use and have only local meaning".
625    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
626        there was a conditional group that depended on an assertion, if the
627        assertion was false, the callout that immediately followed the alternation
628        in the condition was skipped when pcre_exec() was used for matching.
630    23. Allow an explicit callout to be inserted before an assertion that is the
631        condition for a conditional group, for compatibility with automatic
632        callouts, which always insert a callout at this point.
634    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
635        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
637    25. (*PRUNE) is now supported by the JIT compiler.
639    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
641    27. Fix the case where there are two or more SKIPs with arguments that may be
642        ignored.
644    28. (*SKIP) is now supported by the JIT compiler.
646    29. (*THEN) is now supported by the JIT compiler.
648    30. Update RunTest with additional test selector options.
650    31. The way PCRE handles backtracking verbs has been changed in two ways.
652        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
653        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
654        backtracking. In some cases this makes it more Perl-compatible, but Perl's
655        rather obscure rules do not always do the same thing.
657        (2) Previously, backtracking verbs were confined within assertions. This is
658        no longer the case for positive assertions, except for (*ACCEPT). Again,
659        this sometimes improves Perl compatibility, and sometimes does not.
661    32. A number of tests that were in test 2 because Perl did things differently
662        have been moved to test 1, because either Perl or PCRE has changed, and
663        these tests are now compatible.
665    32. Backtracking control verbs are now handled in the same way in JIT and
666        interpreter.
668    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
669        contained a forward subroutine reference caused a compile error.
671    34. Auto-detect and optimize limited repetitions in JIT.
673    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
674        blocking (*UTF) etc.
676    36. In the interpreter, maximizing pattern repetitions for characters and
677        character types now use tail recursion, which reduces stack usage.
679    37. The value of the max lookbehind was not correctly preserved if a compiled
680        and saved regex was reloaded on a host of different endianness.
682    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
683        of the compiled pattern block, expand the flags field from 16 to 32 bits
684        because it was almost full.
686    39. Try madvise first before posix_madvise.
688    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
689        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
690        original change locked out all matches of empty strings. This has been
691        changed so that one match of an empty string per line is recognized.
692        Subsequent searches on the same line (for colouring or for --only-matching,
693        for example) do not recognize empty strings.
695    41. Applied a user patch to fix a number of spelling mistakes in comments.
697    42. Data lines longer than 65536 caused pcretest to crash.
699    43. Clarified the data type for length and startoffset arguments for pcre_exec
700        and pcre_dfa_exec in the function-specific man pages, where they were
701        explicitly stated to be in bytes, never having been updated. I also added
702        some clarification to the pcreapi man page.
704    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
705        a segmentation fault.
708    Version 8.32 30-November-2012
709  -----------------------------  -----------------------------
711    1.  Improved JIT compiler optimizations for first character search and single
712        character iterators.
714    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
715        Patch by Daniel Richard G.
717    3.  Single character iterator optimizations in the JIT compiler.
719    4.  Improved JIT compiler optimizations for character ranges.
721    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
722        Reported by Giuseppe D'Angelo.
724    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
725        of a line, was being set incorrectly in cases where .* appeared inside
726        atomic brackets at the start of a pattern, or where there was a subsequent
727        *PRUNE or *SKIP.
729    7.  Improved instruction cache flush for POWER/PowerPC.
730        Patch by Daniel Richard G.
732    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
733        grep:
735        (a) There is now no limit to the number of patterns to be matched.
737        (b) An error is given if a pattern is too long.
739        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
740            are now supported.
742        (d) --exclude-from and --include-from (multiple use) have been added.
744        (e) Exclusions and inclusions now apply to all files and directories, not
745            just to those obtained from scanning a directory recursively.
747        (f) Multiple uses of -f and --file-list are now supported.
749        (g) In a Windows environment, the default for -d has been changed from
750            "read" (the GNU grep default) to "skip", because otherwise the presence
751            of a directory in the file list provokes an error.
753        (h) The documentation has been revised and clarified in places.
755    9.  Improve the matching speed of capturing brackets.
757    10. Changed the meaning of \X so that it now matches a Unicode extended
758        grapheme cluster.
760    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
761        out POSIX threads when JIT support is configured.
763    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
765    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
766        structure could go wrong in environments where size_t is not the same size
767        as int.
769    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
770        set.
772    15. The EBCDIC support had decayed; later updates to the code had included
773        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
774        general tidy up of EBCDIC-related issues, and the documentation was also
775        not quite right. There is now a test that can be run on ASCII systems to
776        check some of the EBCDIC-related things (but is it not a full test).
778    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
779        in a small tidy to the code.
781    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
783    18. If the --only-matching (-o) option in pcregrep is specified multiple
784        times, each one causes appropriate output. For example, -o1 -o2 outputs the
785        substrings matched by the 1st and 2nd capturing parentheses. A separating
786        string can be specified by --om-separator (default empty).
788    19. Improving the first n character searches.
790    20. Turn case lists for horizontal and vertical white space into macros so that
791        they are defined only once.
793    21. This set of changes together give more compatible Unicode case-folding
794        behaviour for characters that have more than one other case when UCP
795        support is available.
797        (a) The Unicode property table now has offsets into a new table of sets of
798            three or more characters that are case-equivalent. The MultiStage2.py
799            script that generates these tables (the pcre_ucd.c file) now scans
800            CaseFolding.txt instead of UnicodeData.txt for character case
801            information.
803        (b) The code for adding characters or ranges of characters to a character
804            class has been abstracted into a generalized function that also handles
805            case-independence. In UTF-mode with UCP support, this uses the new data
806            to handle characters with more than one other case.
808        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
809            whose other case is greater than 256 are now correctly matched
810            caselessly. Previously, the high codepoint matched the low one, but not
811            vice versa.
813        (d) The processing of \h, \H, \v, and \ in character classes now makes use
814            of the new class addition function, using character lists defined as
815            macros alongside the case definitions of 20 above.
817        (e) Caseless back references now work with characters that have more than
818            one other case.
820        (f) General caseless matching of characters with more than one other case
821            is supported.
823    22. Unicode character properties were updated from Unicode 6.2.0
825    23. Improved CMake support under Windows. Patch by Daniel Richard G.
827    24. Add support for 32-bit character strings, and UTF-32
829    25. Major JIT compiler update (code refactoring and bugfixing).
830        Experimental Sparc 32 support is added.
832    26. Applied a modified version of Daniel Richard G's patch to create
833        pcre.h.generic and config.h.generic by "make" instead of in the
834        PrepareRelease script.
836    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
837        pcre_compile.c when checking for a zero character.
839    28. Introducing a native interface for JIT. Through this interface, the compiled
840        machine code can be directly executed. The purpose of this interface is to
841        provide fast pattern matching, so several sanity checks are not performed.
842        However, feature tests are still performed. The new interface provides
843        1.4x speedup compared to the old one.
845    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
846        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
847        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
849    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
850        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
851        the "old" RFC 2279). Instead, it ended up passing a negative length to
852        pcre_exec().
854    31. Add support for GCC's visibility feature to hide internal functions.
856    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
857        "unknown -C option" after outputting 0 or 1.
859    33. There is now support for generating a code coverage report for the test
860        suite in environments where gcc is the compiler and lcov is installed. This
861        is mainly for the benefit of the developers.
863    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
864        unaddressable using valgrind annotations, allowing valgrind to detect
865        invalid memory accesses. This is mainly for the benefit of the developers.
867    25. (*UTF) can now be used to start a pattern in any of the three libraries.
869    26. Give configure error if --enable-cpp but no C++ compiler found.
872    Version 8.31 06-July-2012
873    -------------------------
875  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
877  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
879  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
880      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
881      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
883  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 886  Version 8.31
886      of more than one character:      of more than one character:
888      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
889          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
890          references.          references.
892      (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
893          subject.          subject.
895      (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
896          characters at the end of the subject.          characters at the end of the subject.
898      (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 901  Version 8.31
901      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
902          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.
904  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
905      running pcretest, the text "(JIT)" added to the output whenever JIT is      running pcretest, the text "(JIT)" added to the output whenever JIT is
906      actually used to run the match.      actually used to run the match.
908  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+[+]
909      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
911  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 914  Version 8.31
915  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
916      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
920  12. Applied a (slightly modified) user-supplied patch that improves performance  12. Applied a (slightly modified) user-supplied patch that improves performance
921      when the heap is used for recursion (compiled with --disable-stack-for-      when the heap is used for recursion (compiled with --disable-stack-for-
922      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
923      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
924      possible. This sometimes gives as much as 30% improvement.      possible. This sometimes gives as much as 30% improvement.
926  13. As documented, (*COMMIT) is now confined to within a recursive subpattern  13. As documented, (*COMMIT) is now confined to within a recursive subpattern
927      call.      call.
929  14. As documented, (*COMMIT) is now confined to within a positive assertion.  14. As documented, (*COMMIT) is now confined to within a positive assertion.
931  15. It is now possible to link pcretest with libedit as an alternative to  15. It is now possible to link pcretest with libedit as an alternative to
932      libreadline.      libreadline.
934  16. (*COMMIT) control verb is now supported by the JIT compiler.  16. (*COMMIT) control verb is now supported by the JIT compiler.
936  6.  The Unicode data tables have been updated to Unicode 6.1.0.  17. The Unicode data tables have been updated to Unicode 6.1.0.
938    18. Added --file-list option to pcregrep.
940    19. Added binary file support to pcregrep, including the -a, --binary-files,
941        -I, and --text options.
943    20. The madvise function is renamed for posix_madvise for QNX compatibility
944        reasons. Fixed by Giuseppe D'Angelo.
946    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
948    22. Changed the option for creating symbolic links for 16-bit man pages from
949        -s to -sf so that re-installing does not cause issues.
951    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
953    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
954        matches in certain environments (the workspace was not being correctly
955        retained). Also added to pcre_dfa_exec() a simple plausibility check on
956        some of the workspace data at the beginning of a restart.
958    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
959        was not doing so when it should - probably a typo introduced by SVN 528
960        (change 8.10/14).
962    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
963        \w+ when the character tables indicated that \x{c4} was a word character.
964        There were several related cases, all because the tests for doing a table
965        lookup were testing for characters less than 127 instead of 255.
967    27. If a pattern contains capturing parentheses that are not used in a match,
968        their slots in the ovector are set to -1. For those that are higher than
969        any matched groups, this happens at the end of processing. In the case when
970        there were back references that the ovector was too small to contain
971        (causing temporary malloc'd memory to be used during matching), and the
972        highest capturing number was not used, memory off the end of the ovector
973        was incorrectly being set to -1. (It was using the size of the temporary
974        memory instead of the true size.)
976    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
977        ovector size, it uses memory at the end of the block that it has got.
979    29. Check for an overlong MARK name and give an error at compile time. The
980        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
982    30. JIT compiler update.
984    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
985        Rill for the patch.
987    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
989    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
991    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
992        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
993        was enabled.
995    35. Improve JIT code generation for greedy plus quantifier.
997    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
998        1 to "aa" instead of to an empty string. The bug affected repeated groups
999        that could potentially match an empty string.
1001    37. Optimizing single character iterators in JIT.
1003    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
1004        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
1005        codepoints that are too big for the mode are faulted, and in a UTF mode,
1006        disallowed codepoints are also faulted.
1008    39. If PCRE was compiled with UTF support, in three places in the DFA
1009        matcher there was code that should only have been obeyed in UTF mode, but
1010        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
1011        processing when bytes with values greater than 127 were present. In 16-bit
1012        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
1013        both cases the values are those that cannot be the first data item in a UTF
1014        character. The three items that might have provoked this were recursions,
1015        possessively repeated groups, and atomic groups.
1017    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
1018        and pcregrep, because some OS require shared objects to be explicitly
1019        passed to ld, causing the link step to fail if they are not.
1021    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
1022        mode, patterns that started with \h* or \R* might be incorrectly matched.
1025  Version 8.30 04-February-2012  Version 8.30 04-February-2012
# Line 1258  Version 7.9 11-Apr-09 Line 2212  Version 7.9 11-Apr-09
2212  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
2213      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
2214      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2215      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2216        8.33.]
2218  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
2219      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 1501  Version 7.7 07-May-08 Line 2456  Version 7.7 07-May-08
2456      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2457      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2458      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2459      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2460      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2461      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.942  
changed lines
  Added in v.1534

  ViewVC Help
Powered by ViewVC 1.1.5