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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1033  
changed lines
  Added in v.1560

  ViewVC Help
Powered by ViewVC 1.1.5