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

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

  ViewVC Help
Powered by ViewVC 1.1.5