ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 1322 by zherczeg, Wed May 1 19:42:31 2013 UTC revision 1566 by ph10, Tue Jun 9 17:45:25 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.33 28-April-2013  Note that the PCRE 8.xx series (PCRE1) is now in a bugfix-only state. All
5    development is happening in the PCRE2 10.xx series.
7    Version 8.38 xx-xxx-xxxx
8    ------------------------
10    1.  If a group that contained a recursive back reference also contained a
11        forward reference subroutine call followed by a non-forward-reference
12        subroutine call, for example /.((?2)(?R)\1)()/, pcre2_compile() failed to
13        compile correct code, leading to undefined behaviour or an internally
14        detected error. This bug was discovered by the LLVM fuzzer.
16    2.  Quantification of certain items (e.g. atomic back references) could cause
17        incorrect code to be compiled when recursive forward references were
18        involved. For example, in this pattern: /(?1)()((((((\1++))\x85)+)|))/.
19        This bug was discovered by the LLVM fuzzer.
21    3.  A repeated conditional group whose condition was a reference by name caused
22        a buffer overflow if there was more than one group with the given name.
23        This bug was discovered by the LLVM fuzzer.
25    4.  A recursive back reference by name within a group that had the same name as
26        another group caused a buffer overflow. For example:
27        /(?J)(?'d'(?'d'\g{d}))/. This bug was discovered by the LLVM fuzzer.
29    5.  A forward reference by name to a group whose number is the same as the
30        current group, for example in this pattern: /(?|(\k'Pm')|(?'Pm'))/, caused
31        a buffer overflow at compile time. This bug was discovered by the LLVM
32        fuzzer.
34    6.  A lookbehind assertion within a set of mutually recursive subpatterns could
35        provoke a buffer overflow. This bug was discovered by the LLVM fuzzer.
37    7.  Another buffer overflow bug involved duplicate named groups with a
38        reference between their definition, with a group that reset capture
39        numbers, for example: /(?J:(?|(?'R')(\k'R')|((?'R'))))/. This has been
40        fixed by always allowing for more memory, even if not needed. (A proper fix
41        is implemented in PCRE2, but it involves more refactoring.)
43    8.  There was no check for integer overflow in subroutine calls such as (?123).
45    9.  The table entry for \l in EBCDIC environments was incorrect, leading to its
46        being treated as a literal 'l' instead of causing an error.
48    10. There was a buffer overflow if pcre_exec() was called with an ovector of
49        size 1. This bug was found by american fuzzy lop.
51    11. If a non-capturing group containing a conditional group that could match
52        an empty string was repeated, it was not identified as matching an empty
53        string itself. For example: /^(?:(?(1)x|)+)+$()/.
56    Version 8.37 28-April-2015
57    --------------------------
59    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
60        for those parentheses to be closed with whatever has been captured so far.
61        However, it was failing to mark any other groups between the hightest
62        capture so far and the currrent group as "unset". Thus, the ovector for
63        those groups contained whatever was previously there. An example is the
64        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
66    2.  If an assertion condition was quantified with a minimum of zero (an odd
67        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
69    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
70        unrecognized modifier, a crash could occur.
72    4.  An attempt to do global matching in pcretest with a zero-length ovector
73        caused a crash.
75    5.  Fixed a memory leak during matching that could occur for a subpattern
76        subroutine call (recursive or otherwise) if the number of captured groups
77        that had to be saved was greater than ten.
79    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
80        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
81        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
83    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
84        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
86    8. When a pattern is compiled, it remembers the highest back reference so that
87       when matching, if the ovector is too small, extra memory can be obtained to
88       use instead. A conditional subpattern whose condition is a check on a
89       capture having happened, such as, for example in the pattern
90       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
91       setting the highest backreference number. This mattered only if pcre_exec()
92       was called with an ovector that was too small to hold the capture, and there
93       was no other kind of back reference (a situation which is probably quite
94       rare). The effect of the bug was that the condition was always treated as
95       FALSE when the capture could not be consulted, leading to a incorrect
96       behaviour by pcre_exec(). This bug has been fixed.
98    9. A reference to a duplicated named group (either a back reference or a test
99       for being set in a conditional) that occurred in a part of the pattern where
100       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
101       to be incorrectly calculated, leading to overwriting.
103    10. A mutually recursive set of back references such as (\2)(\1) caused a
104        segfault at study time (while trying to find the minimum matching length).
105        The infinite loop is now broken (with the minimum length unset, that is,
106        zero).
108    11. If an assertion that was used as a condition was quantified with a minimum
109        of zero, matching went wrong. In particular, if the whole group had
110        unlimited repetition and could match an empty string, a segfault was
111        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
112        assertions to be quantified, but not if they are being used as conditions,
113        so the above pattern is faulted by Perl. PCRE has now been changed so that
114        it also rejects such patterns.
116    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
117        failed to allow the zero-repeat case if pcre2_exec() was called with an
118        ovector too small to capture the group.
120    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
121        Red Hat Product Security:
123        (a) A crash if /K and /F were both set with the option to save the compiled
124        pattern.
126        (b) Another crash if the option to print captured substrings in a callout
127        was combined with setting a null ovector, for example \O\C+ as a subject
128        string.
130    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
131        forward reference repeated a large (but limited) number of times within a
132        repeated outer group that has a zero minimum quantifier, caused incorrect
133        code to be compiled, leading to the error "internal error:
134        previously-checked referenced subpattern not found" when an incorrect
135        memory address was read. This bug was reported as "heap overflow",
136        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
137        CVE-2015-2325.
139    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
140        call within a group that also contained a recursive back reference caused
141        incorrect code to be compiled. This bug was reported as "heap overflow",
142        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
143        number CVE-2015-2326.
145    24. Computing the size of the JIT read-only data in advance has been a source
146        of various issues, and new ones are still appear unfortunately. To fix
147        existing and future issues, size computation is eliminated from the code,
148        and replaced by on-demand memory allocation.
150    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
151        adjacent to the end of the range, and the range contained characters with
152        more than one other case, caused incorrect behaviour when compiled in UTF
153        mode. In that example, the range a-j was left out of the class.
155    26. Fix JIT compilation of conditional blocks, which assertion
156        is converted to (*FAIL). E.g: /(?(?!))/.
158    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
159        discovered by the LLVM fuzzer.
161    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
162        when this assertion was used as a condition, for example (?(?!)a|b). In
163        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
164        error about an unsupported item.
166    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
167        possessification code could take exponential time to complete. A recursion
168        depth limit of 1000 has been imposed to limit the resources used by this
169        optimization.
171    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
172        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
173        because \S ensures they are all in the class. The code for doing this was
174        interacting badly with the code for computing the amount of space needed to
175        compile the pattern, leading to a buffer overflow. This bug was discovered
176        by the LLVM fuzzer.
178    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
179        other kinds of group caused stack overflow at compile time. This bug was
180        discovered by the LLVM fuzzer.
182    32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
183        between a subroutine call and its quantifier was incorrectly compiled,
184        leading to buffer overflow or other errors. This bug was discovered by the
185        LLVM fuzzer.
187    33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
188        assertion after (?(. The code was failing to check the character after
189        (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
190        was discovered by the LLVM fuzzer.
192    34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
193        a fixed maximum following a group that contains a subroutine reference was
194        incorrectly compiled and could trigger buffer overflow. This bug was
195        discovered by the LLVM fuzzer.
197    35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
198        caused a stack overflow instead of the diagnosis of a non-fixed length
199        lookbehind assertion. This bug was discovered by the LLVM fuzzer.
201    36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
202        (e.g. /(?<=\Ka)/) could make pcregrep loop.
204    37. There was a similar problem to 36 in pcretest for global matches.
206    38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
207        and a subsequent item in the pattern caused a non-match, backtracking over
208        the repeated \X did not stop, but carried on past the start of the subject,
209        causing reference to random memory and/or a segfault. There were also some
210        other cases where backtracking after \C could crash. This set of bugs was
211        discovered by the LLVM fuzzer.
213    39. The function for finding the minimum length of a matching string could take
214        a very long time if mutual recursion was present many times in a pattern,
215        for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
216        method has been implemented. This infelicity was discovered by the LLVM
217        fuzzer.
219    40. Static linking against the PCRE library using the pkg-config module was
220        failing on missing pthread symbols.
223    Version 8.36 26-September-2014
224    ------------------------------
226    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
227        -Wmissing-field-initializers and -Wunused-parameter.
229    2.  The tests for quantifiers being too big (greater than 65535) were being
230        applied after reading the number, and stupidly assuming that integer
231        overflow would give a negative number. The tests are now applied as the
232        numbers are read.
234    3.  Tidy code in pcre_exec.c where two branches that used to be different are
235        now the same.
237    4.  The JIT compiler did not generate match limit checks for certain
238        bracketed expressions with quantifiers. This may lead to exponential
239        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
240        issue should be resolved now.
242    5.  Fixed an issue, which occures when nested alternatives are optimized
243        with table jumps.
245    6.  Inserted two casts and changed some ints to size_t in the light of some
246        reported 64-bit compiler warnings (Bugzilla 1477).
248    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
249        an empty string, which sometimes were behaving incorrectly in the
250        interpreter (though correctly in the JIT matcher). This pcretest input is
251        an example:
253          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
256        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
257        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
258        for an empty string was breaking the inner loop and carrying on at a lower
259        level, when possessive repeated groups should always return to a higher
260        level as they have no backtrack points in them. The empty string test now
261        occurs at the outer level.
263    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
264        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
266    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
267        doesn't).
269    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
270        to hold a pattern to be incorrectly computed (too small) when there were
271        named back references to duplicated names. This could cause "internal
272        error: code overflow" or "double free or corruption" or other memory
273        handling errors.
275    11. When named subpatterns had the same prefixes, back references could be
276        confused. For example, in this pattern:
278          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
280        the reference to 'Name' was incorrectly treated as a reference to a
281        duplicate name.
283    12. A pattern such as /^s?c/mi8 where the optional character has more than
284        one "other case" was incorrectly compiled such that it would only try to
285        match starting at "c".
287    13. When a pattern starting with \s was studied, VT was not included in the
288        list of possible starting characters; this should have been part of the
289        8.34/18 patch.
291    14. If a character class started [\Qx]... where x is any character, the class
292        was incorrectly terminated at the ].
294    15. If a pattern that started with a caseless match for a character with more
295        than one "other case" was studied, PCRE did not set up the starting code
296        unit bit map for the list of possible characters. Now it does. This is an
297        optimization improvement, not a bug fix.
299    16. The Unicode data tables have been updated to Unicode 7.0.0.
301    17. Fixed a number of memory leaks in pcregrep.
303    18. Avoid a compiler warning (from some compilers) for a function call with
304        a cast that removes "const" from an lvalue by using an intermediate
305        variable (to which the compiler does not object).
307    19. Incorrect code was compiled if a group that contained an internal recursive
308        back reference was optional (had quantifier with a minimum of zero). This
309        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
310        caused segmentation faults because of stack overflows at compile time.
312    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
313        group that is quantified with an indefinite repeat, caused a compile-time
314        loop which used up all the system stack and provoked a segmentation fault.
315        This was not the same bug as 19 above.
317    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
318        Patch by Mike Frysinger.
321    Version 8.35 04-April-2014
322  --------------------------  --------------------------
324    1.  A new flag is set, when property checks are present in an XCLASS.
325        When this flag is not set, PCRE can perform certain optimizations
326        such as studying these XCLASS-es.
328    2.  The auto-possessification of character sets were improved: a normal
329        and an extended character set can be compared now. Furthermore
330        the JIT compiler optimizes more character set checks.
332    3.  Got rid of some compiler warnings for potentially uninitialized variables
333        that show up only when compiled with -O2.
335    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
336        of a match later then the end of the match. The pcretest program was not
337        handling the case sensibly - it was outputting from the start to the next
338        binary zero. It now reports this situation in a message, and outputs the
339        text from the end to the start.
341    5.  Fast forward search is improved in JIT. Instead of the first three
342        characters, any three characters with fixed position can be searched.
343        Search order: first, last, middle.
345    6.  Improve character range checks in JIT. Characters are read by an inprecise
346        function now, which returns with an unknown value if the character code is
347        above a certain threshold (e.g: 256). The only limitation is that the value
348        must be bigger than the threshold as well. This function is useful when
349        the characters above the threshold are handled in the same way.
351    7.  The macros whose names start with RAWUCHAR are placeholders for a future
352        mode in which only the bottom 21 bits of 32-bit data items are used. To
353        make this more memorable for those maintaining the code, the names have
354        been changed to start with UCHAR21, and an extensive comment has been added
355        to their definition.
357    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
358        to the export list in Makefile.am (they were accidentally omitted from the
359        8.34 tarball).
361    9.  The informational output from pcretest used the phrase "starting byte set"
362        which is inappropriate for the 16-bit and 32-bit libraries. As the output
363        for "first char" and "need char" really means "non-UTF-char", I've changed
364        "byte" to "char", and slightly reworded the output. The documentation about
365        these values has also been (I hope) clarified.
367    10. Another JIT related optimization: use table jumps for selecting the correct
368        backtracking path, when more than four alternatives are present inside a
369        bracket.
371    11. Empty match is not possible, when the minimum length is greater than zero,
372        and there is no \K in the pattern. JIT should avoid empty match checks in
373        such cases.
375    12. In a caseless character class with UCP support, when a character with more
376        than one alternative case was not the first character of a range, not all
377        the alternative cases were added to the class. For example, s and \x{17f}
378        are both alternative cases for S: the class [RST] was handled correctly,
379        but [R-T] was not.
381    13. The configure.ac file always checked for pthread support when JIT was
382        enabled. This is not used in Windows, so I have put this test inside a
383        check for the presence of windows.h (which was already tested for).
385    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
386        The algorithm provides a way to skip certain starting offsets, and usually
387        faster than linear prefix searches.
389    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
390        as for 'fr_FR' and 'french'. For some reason, however, it then used the
391        Windows-specific input and output files, which have 'french' screwed in.
392        So this could never have worked. One of the problems with locales is that
393        they aren't always the same. I have now updated RunTest so that it checks
394        the output of the locale test (test 3) against three different output
395        files, and it allows the test to pass if any one of them matches. With luck
396        this should make the test pass on some versions of Solaris where it was
397        failing. Because of the uncertainty, the script did not used to stop if
398        test 3 failed; it now does. If further versions of a French locale ever
399        come to light, they can now easily be added.
401    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
402        there was a message during ./configure, but it did not stop. This now
403        provokes an error. The invalid example in README has been corrected.
404        If a value less than the minimum is given, the minimum value has always
405        been used, but now a warning is given.
407    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
408        was a bug in the test system, which is now fixed. Also, the list of various
409        configurations that are tested for each release did not have one with both
410        16/32 bits and --enable-bar-anycrlf. It now does.
412    18. pcretest was missing "-C bsr" for displaying the \R default setting.
414    19. Little endian PowerPC systems are supported now by the JIT compiler.
416    20. The fast forward newline mechanism could enter to an infinite loop on
417        certain invalid UTF-8 input. Although we don't support these cases
418        this issue can be fixed by a performance optimization.
420    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
421        not take account if existing stack usage. There is now a new global
422        variable called pcre_stack_guard that can be set to point to an external
423        function to check stack availability. It is called at the start of
424        processing every parenthesized group.
426    22. A typo in the code meant that in ungreedy mode the max/min qualifier
427        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
428        not match "ab".
430    23. When UTF was disabled, the JIT program reported some incorrect compile
431        errors. These messages are silenced now.
433    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
434        compiler.
436    25. Change all the temporary files used in RunGrepTest to be different to those
437        used by RunTest so that the tests can be run simultaneously, for example by
438        "make -j check".
441    Version 8.34 15-December-2013
442    -----------------------------
444    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
445        executable memory. Patch inspired by Carsten Klein.
447    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
448        this macro is never tested and has no effect, because the work to support
449        coverage involves only compiling and linking options and special targets in
450        the Makefile. The comment in config.h implied that defining the macro would
451        enable coverage support, which is totally false. There was also support for
452        setting this macro in the CMake files (my fault, I just copied it from
453        configure). SUPPORT_GCOV has now been removed.
455    3.  Make a small performance improvement in strlen16() and strlen32() in
456        pcretest.
458    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
459        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
460        these cases). There was also one in pcretest.c.
462    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
464    6.  In UTF mode, the code for checking whether a group could match an empty
465        string (which is used for indefinitely repeated groups to allow for
466        breaking an infinite loop) was broken when the group contained a repeated
467        negated single-character class with a character that occupied more than one
468        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
469        UTF-8 mode). The effect was undefined: the group might or might not be
470        deemed as matching an empty string, or the program might have crashed.
472    7.  The code for checking whether a group could match an empty string was not
473        recognizing that \h, \H, \v, \V, and \R must match a character.
475    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
476        an empty string. If it can, pcretest shows this in its information output.
478    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
479        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
480        matched by pcre_exec() without using JIT:
482        (a) If the rest of the pattern did not match after a maximal run of
483            grapheme clusters, the code for backing up to try with fewer of them
484            did not always back up over a full grapheme when characters that do not
485            have the modifier quality were involved, e.g. Hangul syllables.
487        (b) If the match point in a subject started with modifier character, and
488            there was no match, the code could incorrectly back up beyond the match
489            point, and potentially beyond the first character in the subject,
490            leading to a segfault or an incorrect match result.
492    10. A conditional group with an assertion condition could lead to PCRE
493        recording an incorrect first data item for a match if no other first data
494        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
495        first data item, and therefore matched "ca" after "c" instead of at the
496        start.
498    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
499        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
501    12. The source of pcregrep now includes z/OS-specific code so that it can be
502        compiled for z/OS as part of the special z/OS distribution.
504    13. Added the -T and -TM options to pcretest.
506    14. The code in pcre_compile.c for creating the table of named capturing groups
507        has been refactored. Instead of creating the table dynamically during the
508        actual compiling pass, the information is remembered during the pre-compile
509        pass (on the stack unless there are more than 20 named groups, in which
510        case malloc() is used) and the whole table is created before the actual
511        compile happens. This has simplified the code (it is now nearly 150 lines
512        shorter) and prepared the way for better handling of references to groups
513        with duplicate names.
515    15. A back reference to a named subpattern when there is more than one of the
516        same name now checks them in the order in which they appear in the pattern.
517        The first one that is set is used for the reference. Previously only the
518        first one was inspected. This change makes PCRE more compatible with Perl.
520    16. Unicode character properties were updated from Unicode 6.3.0.
522    17. The compile-time code for auto-possessification has been refactored, based
523        on a patch by Zoltan Herczeg. It now happens after instead of during
524        compilation. The code is cleaner, and more cases are handled. The option
525        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
526        options in pcretest are provided to set it. It can also be set by
527        (*NO_AUTO_POSSESS) at the start of a pattern.
529    18. The character VT has been added to the default ("C" locale) set of
530        characters that match \s and are generally treated as white space,
531        following this same change in Perl 5.18. There is now no difference between
532        "Perl space" and "POSIX space". Whether VT is treated as white space in
533        other locales depends on the locale.
535    19. The code for checking named groups as conditions, either for being set or
536        for being recursed, has been refactored (this is related to 14 and 15
537        above). Processing unduplicated named groups should now be as fast at
538        numerical groups, and processing duplicated groups should be faster than
539        before.
541    20. Two patches to the CMake build system, by Alexander Barkov:
543          (1) Replace the "source" command by "." in CMakeLists.txt because
544              "source" is a bash-ism.
546          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
547              without these the CMake build does not work on Solaris.
549    21. Perl has changed its handling of \8 and \9. If there is no previously
550        encountered capturing group of those numbers, they are treated as the
551        literal characters 8 and 9 instead of a binary zero followed by the
552        literals. PCRE now does the same.
554    22. Following Perl, added \o{} to specify codepoints in octal, making it
555        possible to specify values greater than 0777 and also making them
556        unambiguous.
558    23. Perl now gives an error for missing closing braces after \x{... instead of
559        treating the string as literal. PCRE now does the same.
561    24. RunTest used to grumble if an inappropriate test was selected explicitly,
562        but just skip it when running all tests. This make it awkward to run ranges
563        of tests when one of them was inappropriate. Now it just skips any
564        inappropriate tests, as it always did when running all tests.
566    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
567        character types such as \d or \w, too many callouts were inserted, and the
568        data that they returned was rubbish.
570    26. In UCP mode, \s was not matching two of the characters that Perl matches,
571        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
572        were matched by \h. The code has now been refactored so that the lists of
573        the horizontal and vertical whitespace characters used for \h and \v (which
574        are defined only in one place) are now also used for \s.
576    27. Add JIT support for the 64 bit TileGX architecture.
577        Patch by Jiong Wang (Tilera Corporation).
579    28. Possessive quantifiers for classes (both explicit and automatically
580        generated) now use special opcodes instead of wrapping in ONCE brackets.
582    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
583        (because it's meaningless), this was not happening when PCRE_CASELESS was
584        set. Not wrong, but inefficient.
586    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
587        properties for \w, \d, etc) is present in a test regex. Otherwise if the
588        test contains no characters greater than 255, Perl doesn't realise it
589        should be using Unicode semantics.
591    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
592        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
593        does in Unicode mode.
595    32. Added the "forbid" facility to pcretest so that putting tests into the
596        wrong test files can sometimes be quickly detected.
598    33. There is now a limit (default 250) on the depth of nesting of parentheses.
599        This limit is imposed to control the amount of system stack used at compile
600        time. It can be changed at build time by --with-parens-nest-limit=xxx or
601        the equivalent in CMake.
603    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
604        errors. Perl warns for these when in warning mode, but PCRE has no facility
605        for giving warnings.
607    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
608        However, this was not working for (?!) because it is optimized to (*FAIL),
609        for which PCRE does not allow quantifiers. The optimization is now disabled
610        when a quantifier follows (?!). I can't see any use for this, but it makes
611        things uniform.
613    36. Perl no longer allows group names to start with digits, so I have made this
614        change also in PCRE. It simplifies the code a bit.
616    37. In extended mode, Perl ignores spaces before a + that indicates a
617        possessive quantifier. PCRE allowed a space before the quantifier, but not
618        before the possessive +. It now does.
620    38. The use of \K (reset reported match start) within a repeated possessive
621        group such as (a\Kb)*+ was not working.
623    40. Document that the same character tables must be used at compile time and
624        run time, and that the facility to pass tables to pcre_exec() and
625        pcre_dfa_exec() is for use only with saved/restored patterns.
627    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
628        features for Builds with MSVC:
630        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
631           builds). The .rc files can be used to set FileDescription and many other
632           attributes.
634        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
635           This allows higher-level build scripts which want .pdb files to avoid
636           hard-coding the exact files needed."
638    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
639        mean "start of word" and "end of word", respectively, as a transition aid.
641    43. A minimizing repeat of a class containing codepoints greater than 255 in
642        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
643        compiled to use the heap for recursion.
645    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
646        is configured.
649    Version 8.33 28-May-2013
650    ------------------------
652  1.  Added 'U' to some constants that are compared to unsigned integers, to  1.  Added 'U' to some constants that are compared to unsigned integers, to
653      avoid compiler signed/unsigned warnings. Added (int) casts to unsigned      avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
654      variables that are added to signed variables, to ensure the result is      variables that are added to signed variables, to ensure the result is
# Line 36  Version 8.33 28-April-2013 Line 681  Version 8.33 28-April-2013
682  9.  Optimizing fast_forward_start_bits in JIT.  9.  Optimizing fast_forward_start_bits in JIT.
684  10. Adding experimental support for callouts in JIT, and fixing some  10. Adding support for callouts in JIT, and fixing some issues revealed
685      issues revealed during this work. Namely:      during this work. Namely:
687      (a) Unoptimized capturing brackets incorrectly reset on backtrack.      (a) Unoptimized capturing brackets incorrectly reset on backtrack.
# Line 125  Version 8.33 28-April-2013 Line 770  Version 8.33 28-April-2013
770      have been moved to test 1, because either Perl or PCRE has changed, and      have been moved to test 1, because either Perl or PCRE has changed, and
771      these tests are now compatible.      these tests are now compatible.
773  32. Control verbs are handled in the same way in JIT and interpreter.  32. Backtracking control verbs are now handled in the same way in JIT and
774        interpreter.
776  33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that  33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
777      contained a forward subroutine reference caused a compile error.      contained a forward subroutine reference caused a compile error.
# Line 147  Version 8.33 28-April-2013 Line 793  Version 8.33 28-April-2013
794  39. Try madvise first before posix_madvise.  39. Try madvise first before posix_madvise.
796    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
797        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
798        original change locked out all matches of empty strings. This has been
799        changed so that one match of an empty string per line is recognized.
800        Subsequent searches on the same line (for colouring or for --only-matching,
801        for example) do not recognize empty strings.
803    41. Applied a user patch to fix a number of spelling mistakes in comments.
805    42. Data lines longer than 65536 caused pcretest to crash.
807    43. Clarified the data type for length and startoffset arguments for pcre_exec
808        and pcre_dfa_exec in the function-specific man pages, where they were
809        explicitly stated to be in bytes, never having been updated. I also added
810        some clarification to the pcreapi man page.
812    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
813        a segmentation fault.
816  Version 8.32 30-November-2012  Version 8.32 30-November-2012
817  -----------------------------  -----------------------------
# Line 1655  Version 7.9 11-Apr-09 Line 2320  Version 7.9 11-Apr-09
2320  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
2321      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
2322      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2323      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2324        8.33.]
2326  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
2327      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 1898  Version 7.7 07-May-08 Line 2564  Version 7.7 07-May-08
2564      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2565      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2566      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2567      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2568      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2569      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.1322  
changed lines
  Added in v.1566

  ViewVC Help
Powered by ViewVC 1.1.5