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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1041  
changed lines
  Added in v.1547

  ViewVC Help
Powered by ViewVC 1.1.5