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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1253  
changed lines
  Added in v.1592

  ViewVC Help
Powered by ViewVC 1.1.5