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

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

  ViewVC Help
Powered by ViewVC 1.1.5