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

Diff of /code/trunk/ChangeLog

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

revision 1394 by ph10, Sat Nov 9 09:17:20 2013 UTC revision 1588 by ph10, Mon Aug 10 14:09:19 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.34 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    
121    Version 8.37 28-April-2015
122    --------------------------
123    
124    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
125        for those parentheses to be closed with whatever has been captured so far.
126        However, it was failing to mark any other groups between the hightest
127        capture so far and the currrent group as "unset". Thus, the ovector for
128        those groups contained whatever was previously there. An example is the
129        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
130    
131    2.  If an assertion condition was quantified with a minimum of zero (an odd
132        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
133    
134    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
135        unrecognized modifier, a crash could occur.
136    
137    4.  An attempt to do global matching in pcretest with a zero-length ovector
138        caused a crash.
139    
140    5.  Fixed a memory leak during matching that could occur for a subpattern
141        subroutine call (recursive or otherwise) if the number of captured groups
142        that had to be saved was greater than ten.
143    
144    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
145        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
146        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
147    
148    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
149        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
150    
151    8. When a pattern is compiled, it remembers the highest back reference so that
152       when matching, if the ovector is too small, extra memory can be obtained to
153       use instead. A conditional subpattern whose condition is a check on a
154       capture having happened, such as, for example in the pattern
155       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
156       setting the highest backreference number. This mattered only if pcre_exec()
157       was called with an ovector that was too small to hold the capture, and there
158       was no other kind of back reference (a situation which is probably quite
159       rare). The effect of the bug was that the condition was always treated as
160       FALSE when the capture could not be consulted, leading to a incorrect
161       behaviour by pcre_exec(). This bug has been fixed.
162    
163    9. A reference to a duplicated named group (either a back reference or a test
164       for being set in a conditional) that occurred in a part of the pattern where
165       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
166       to be incorrectly calculated, leading to overwriting.
167    
168    10. A mutually recursive set of back references such as (\2)(\1) caused a
169        segfault at study time (while trying to find the minimum matching length).
170        The infinite loop is now broken (with the minimum length unset, that is,
171        zero).
172    
173    11. If an assertion that was used as a condition was quantified with a minimum
174        of zero, matching went wrong. In particular, if the whole group had
175        unlimited repetition and could match an empty string, a segfault was
176        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
177        assertions to be quantified, but not if they are being used as conditions,
178        so the above pattern is faulted by Perl. PCRE has now been changed so that
179        it also rejects such patterns.
180    
181    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
182        failed to allow the zero-repeat case if pcre2_exec() was called with an
183        ovector too small to capture the group.
184    
185    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
186        Red Hat Product Security:
187    
188        (a) A crash if /K and /F were both set with the option to save the compiled
189        pattern.
190    
191        (b) Another crash if the option to print captured substrings in a callout
192        was combined with setting a null ovector, for example \O\C+ as a subject
193        string.
194    
195    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
196        forward reference repeated a large (but limited) number of times within a
197        repeated outer group that has a zero minimum quantifier, caused incorrect
198        code to be compiled, leading to the error "internal error:
199        previously-checked referenced subpattern not found" when an incorrect
200        memory address was read. This bug was reported as "heap overflow",
201        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
202        CVE-2015-2325.
203    
204    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
205        call within a group that also contained a recursive back reference caused
206        incorrect code to be compiled. This bug was reported as "heap overflow",
207        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
208        number CVE-2015-2326.
209    
210    24. Computing the size of the JIT read-only data in advance has been a source
211        of various issues, and new ones are still appear unfortunately. To fix
212        existing and future issues, size computation is eliminated from the code,
213        and replaced by on-demand memory allocation.
214    
215    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
216        adjacent to the end of the range, and the range contained characters with
217        more than one other case, caused incorrect behaviour when compiled in UTF
218        mode. In that example, the range a-j was left out of the class.
219    
220    26. Fix JIT compilation of conditional blocks, which assertion
221        is converted to (*FAIL). E.g: /(?(?!))/.
222    
223    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
224        discovered by the LLVM fuzzer.
225    
226    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
227        when this assertion was used as a condition, for example (?(?!)a|b). In
228        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
229        error about an unsupported item.
230    
231    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
232        possessification code could take exponential time to complete. A recursion
233        depth limit of 1000 has been imposed to limit the resources used by this
234        optimization.
235    
236    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
237        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
238        because \S ensures they are all in the class. The code for doing this was
239        interacting badly with the code for computing the amount of space needed to
240        compile the pattern, leading to a buffer overflow. This bug was discovered
241        by the LLVM fuzzer.
242    
243    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
244        other kinds of group caused stack overflow at compile time. This bug was
245        discovered by the LLVM fuzzer.
246    
247    32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
248        between a subroutine call and its quantifier was incorrectly compiled,
249        leading to buffer overflow or other errors. This bug was discovered by the
250        LLVM fuzzer.
251    
252    33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
253        assertion after (?(. The code was failing to check the character after
254        (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
255        was discovered by the LLVM fuzzer.
256    
257    34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
258        a fixed maximum following a group that contains a subroutine reference was
259        incorrectly compiled and could trigger buffer overflow. This bug was
260        discovered by the LLVM fuzzer.
261    
262    35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
263        caused a stack overflow instead of the diagnosis of a non-fixed length
264        lookbehind assertion. This bug was discovered by the LLVM fuzzer.
265    
266    36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
267        (e.g. /(?<=\Ka)/) could make pcregrep loop.
268    
269    37. There was a similar problem to 36 in pcretest for global matches.
270    
271    38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
272        and a subsequent item in the pattern caused a non-match, backtracking over
273        the repeated \X did not stop, but carried on past the start of the subject,
274        causing reference to random memory and/or a segfault. There were also some
275        other cases where backtracking after \C could crash. This set of bugs was
276        discovered by the LLVM fuzzer.
277    
278    39. The function for finding the minimum length of a matching string could take
279        a very long time if mutual recursion was present many times in a pattern,
280        for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
281        method has been implemented. This infelicity was discovered by the LLVM
282        fuzzer.
283    
284    40. Static linking against the PCRE library using the pkg-config module was
285        failing on missing pthread symbols.
286    
287    
288    Version 8.36 26-September-2014
289    ------------------------------
290    
291    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
292        -Wmissing-field-initializers and -Wunused-parameter.
293    
294    2.  The tests for quantifiers being too big (greater than 65535) were being
295        applied after reading the number, and stupidly assuming that integer
296        overflow would give a negative number. The tests are now applied as the
297        numbers are read.
298    
299    3.  Tidy code in pcre_exec.c where two branches that used to be different are
300        now the same.
301    
302    4.  The JIT compiler did not generate match limit checks for certain
303        bracketed expressions with quantifiers. This may lead to exponential
304        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
305        issue should be resolved now.
306    
307    5.  Fixed an issue, which occures when nested alternatives are optimized
308        with table jumps.
309    
310    6.  Inserted two casts and changed some ints to size_t in the light of some
311        reported 64-bit compiler warnings (Bugzilla 1477).
312    
313    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
314        an empty string, which sometimes were behaving incorrectly in the
315        interpreter (though correctly in the JIT matcher). This pcretest input is
316        an example:
317    
318          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
319          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
320    
321        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
322        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
323        for an empty string was breaking the inner loop and carrying on at a lower
324        level, when possessive repeated groups should always return to a higher
325        level as they have no backtrack points in them. The empty string test now
326        occurs at the outer level.
327    
328    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
329        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
330    
331    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
332        doesn't).
333    
334    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
335        to hold a pattern to be incorrectly computed (too small) when there were
336        named back references to duplicated names. This could cause "internal
337        error: code overflow" or "double free or corruption" or other memory
338        handling errors.
339    
340    11. When named subpatterns had the same prefixes, back references could be
341        confused. For example, in this pattern:
342    
343          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
344    
345        the reference to 'Name' was incorrectly treated as a reference to a
346        duplicate name.
347    
348    12. A pattern such as /^s?c/mi8 where the optional character has more than
349        one "other case" was incorrectly compiled such that it would only try to
350        match starting at "c".
351    
352    13. When a pattern starting with \s was studied, VT was not included in the
353        list of possible starting characters; this should have been part of the
354        8.34/18 patch.
355    
356    14. If a character class started [\Qx]... where x is any character, the class
357        was incorrectly terminated at the ].
358    
359    15. If a pattern that started with a caseless match for a character with more
360        than one "other case" was studied, PCRE did not set up the starting code
361        unit bit map for the list of possible characters. Now it does. This is an
362        optimization improvement, not a bug fix.
363    
364    16. The Unicode data tables have been updated to Unicode 7.0.0.
365    
366    17. Fixed a number of memory leaks in pcregrep.
367    
368    18. Avoid a compiler warning (from some compilers) for a function call with
369        a cast that removes "const" from an lvalue by using an intermediate
370        variable (to which the compiler does not object).
371    
372    19. Incorrect code was compiled if a group that contained an internal recursive
373        back reference was optional (had quantifier with a minimum of zero). This
374        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
375        caused segmentation faults because of stack overflows at compile time.
376    
377    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
378        group that is quantified with an indefinite repeat, caused a compile-time
379        loop which used up all the system stack and provoked a segmentation fault.
380        This was not the same bug as 19 above.
381    
382    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
383        Patch by Mike Frysinger.
384    
385    
386    Version 8.35 04-April-2014
387  --------------------------  --------------------------
388    
389    1.  A new flag is set, when property checks are present in an XCLASS.
390        When this flag is not set, PCRE can perform certain optimizations
391        such as studying these XCLASS-es.
392    
393    2.  The auto-possessification of character sets were improved: a normal
394        and an extended character set can be compared now. Furthermore
395        the JIT compiler optimizes more character set checks.
396    
397    3.  Got rid of some compiler warnings for potentially uninitialized variables
398        that show up only when compiled with -O2.
399    
400    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
401        of a match later then the end of the match. The pcretest program was not
402        handling the case sensibly - it was outputting from the start to the next
403        binary zero. It now reports this situation in a message, and outputs the
404        text from the end to the start.
405    
406    5.  Fast forward search is improved in JIT. Instead of the first three
407        characters, any three characters with fixed position can be searched.
408        Search order: first, last, middle.
409    
410    6.  Improve character range checks in JIT. Characters are read by an inprecise
411        function now, which returns with an unknown value if the character code is
412        above a certain threshold (e.g: 256). The only limitation is that the value
413        must be bigger than the threshold as well. This function is useful when
414        the characters above the threshold are handled in the same way.
415    
416    7.  The macros whose names start with RAWUCHAR are placeholders for a future
417        mode in which only the bottom 21 bits of 32-bit data items are used. To
418        make this more memorable for those maintaining the code, the names have
419        been changed to start with UCHAR21, and an extensive comment has been added
420        to their definition.
421    
422    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
423        to the export list in Makefile.am (they were accidentally omitted from the
424        8.34 tarball).
425    
426    9.  The informational output from pcretest used the phrase "starting byte set"
427        which is inappropriate for the 16-bit and 32-bit libraries. As the output
428        for "first char" and "need char" really means "non-UTF-char", I've changed
429        "byte" to "char", and slightly reworded the output. The documentation about
430        these values has also been (I hope) clarified.
431    
432    10. Another JIT related optimization: use table jumps for selecting the correct
433        backtracking path, when more than four alternatives are present inside a
434        bracket.
435    
436    11. Empty match is not possible, when the minimum length is greater than zero,
437        and there is no \K in the pattern. JIT should avoid empty match checks in
438        such cases.
439    
440    12. In a caseless character class with UCP support, when a character with more
441        than one alternative case was not the first character of a range, not all
442        the alternative cases were added to the class. For example, s and \x{17f}
443        are both alternative cases for S: the class [RST] was handled correctly,
444        but [R-T] was not.
445    
446    13. The configure.ac file always checked for pthread support when JIT was
447        enabled. This is not used in Windows, so I have put this test inside a
448        check for the presence of windows.h (which was already tested for).
449    
450    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
451        The algorithm provides a way to skip certain starting offsets, and usually
452        faster than linear prefix searches.
453    
454    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
455        as for 'fr_FR' and 'french'. For some reason, however, it then used the
456        Windows-specific input and output files, which have 'french' screwed in.
457        So this could never have worked. One of the problems with locales is that
458        they aren't always the same. I have now updated RunTest so that it checks
459        the output of the locale test (test 3) against three different output
460        files, and it allows the test to pass if any one of them matches. With luck
461        this should make the test pass on some versions of Solaris where it was
462        failing. Because of the uncertainty, the script did not used to stop if
463        test 3 failed; it now does. If further versions of a French locale ever
464        come to light, they can now easily be added.
465    
466    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
467        there was a message during ./configure, but it did not stop. This now
468        provokes an error. The invalid example in README has been corrected.
469        If a value less than the minimum is given, the minimum value has always
470        been used, but now a warning is given.
471    
472    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
473        was a bug in the test system, which is now fixed. Also, the list of various
474        configurations that are tested for each release did not have one with both
475        16/32 bits and --enable-bar-anycrlf. It now does.
476    
477    18. pcretest was missing "-C bsr" for displaying the \R default setting.
478    
479    19. Little endian PowerPC systems are supported now by the JIT compiler.
480    
481    20. The fast forward newline mechanism could enter to an infinite loop on
482        certain invalid UTF-8 input. Although we don't support these cases
483        this issue can be fixed by a performance optimization.
484    
485    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
486        not take account if existing stack usage. There is now a new global
487        variable called pcre_stack_guard that can be set to point to an external
488        function to check stack availability. It is called at the start of
489        processing every parenthesized group.
490    
491    22. A typo in the code meant that in ungreedy mode the max/min qualifier
492        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
493        not match "ab".
494    
495    23. When UTF was disabled, the JIT program reported some incorrect compile
496        errors. These messages are silenced now.
497    
498    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
499        compiler.
500    
501    25. Change all the temporary files used in RunGrepTest to be different to those
502        used by RunTest so that the tests can be run simultaneously, for example by
503        "make -j check".
504    
505    
506    Version 8.34 15-December-2013
507    -----------------------------
508    
509  1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT  1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
510      executable memory. Patch inspired by Carsten Klein.      executable memory. Patch inspired by Carsten Klein.
511    
512  2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although  2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
513      this macro is never tested and has no effect, because the work to support      this macro is never tested and has no effect, because the work to support
514      coverage involves only compiling and linking options and special targets in      coverage involves only compiling and linking options and special targets in
515      the Makefile. The comment in config.h implied that defining the macro would      the Makefile. The comment in config.h implied that defining the macro would
516      enable coverage support, which is totally false. There was also support for      enable coverage support, which is totally false. There was also support for
517      setting this macro in the CMake files (my fault, I just copied it from      setting this macro in the CMake files (my fault, I just copied it from
518      configure). SUPPORT_GCOV has now been removed.      configure). SUPPORT_GCOV has now been removed.
519    
520  3.  Make a small performance improvement in strlen16() and strlen32() in  3.  Make a small performance improvement in strlen16() and strlen32() in
521      pcretest.      pcretest.
522    
523  4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,  4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
524      detected by the Solaris compiler (gcc doesn't seem to be able to diagnose      detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
525      these cases). There was also one in pcretest.c.      these cases). There was also one in pcretest.c.
526    
527  5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.  5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
528    
529  6.  In UTF mode, the code for checking whether a group could match an empty  6.  In UTF mode, the code for checking whether a group could match an empty
530      string (which is used for indefinitely repeated groups to allow for      string (which is used for indefinitely repeated groups to allow for
# Line 31  Version 8.34 xx-xxxx-201x Line 533  Version 8.34 xx-xxxx-201x
533      data item and had a minimum repetition of zero (for example, [^\x{100}]* in      data item and had a minimum repetition of zero (for example, [^\x{100}]* in
534      UTF-8 mode). The effect was undefined: the group might or might not be      UTF-8 mode). The effect was undefined: the group might or might not be
535      deemed as matching an empty string, or the program might have crashed.      deemed as matching an empty string, or the program might have crashed.
536    
537  7.  The code for checking whether a group could match an empty string was not  7.  The code for checking whether a group could match an empty string was not
538      recognizing that \h, \H, \v, \V, and \R must match a character.      recognizing that \h, \H, \v, \V, and \R must match a character.
539    
540  8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match  8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
541      an empty string. If it can, pcretest shows this in its information output.      an empty string. If it can, pcretest shows this in its information output.
542    
543  9.  Fixed two related bugs that applied to Unicode extended grapheme clusters  9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
544      that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when      that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
545      matched by pcre_exec() without using JIT:      matched by pcre_exec() without using JIT:
546    
547      (a) If the rest of the pattern did not match after a maximal run of      (a) If the rest of the pattern did not match after a maximal run of
548          grapheme clusters, the code for backing up to try with fewer of them          grapheme clusters, the code for backing up to try with fewer of them
549          did not always back up over a full grapheme when characters that do not          did not always back up over a full grapheme when characters that do not
550          have the modifier quality were involved, e.g. Hangul syllables.          have the modifier quality were involved, e.g. Hangul syllables.
551    
552      (b) If the match point in a subject started with modifier character, and      (b) If the match point in a subject started with modifier character, and
553          there was no match, the code could incorrectly back up beyond the match          there was no match, the code could incorrectly back up beyond the match
554          point, and potentially beyond the first character in the subject,          point, and potentially beyond the first character in the subject,
555          leading to a segfault or an incorrect match result.          leading to a segfault or an incorrect match result.
556    
557  10. A conditional group with an assertion condition could lead to PCRE  10. A conditional group with an assertion condition could lead to PCRE
558      recording an incorrect first data item for a match if no other first data      recording an incorrect first data item for a match if no other first data
559      item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a      item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
560      first data item, and therefore matched "ca" after "c" instead of at the      first data item, and therefore matched "ca" after "c" instead of at the
561      start.      start.
562    
563  11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a  11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
564      bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.      bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
565    
566  12. The source of pcregrep now includes z/OS-specific code so that it can be  12. The source of pcregrep now includes z/OS-specific code so that it can be
567      compiled for z/OS as part of the special z/OS distribution.      compiled for z/OS as part of the special z/OS distribution.
568    
569  13. Added the -T and -TM options to pcretest.  13. Added the -T and -TM options to pcretest.
570    
571  14. The code in pcre_compile.c for creating the table of named capturing groups  14. The code in pcre_compile.c for creating the table of named capturing groups
572      has been refactored. Instead of creating the table dynamically during the      has been refactored. Instead of creating the table dynamically during the
573      actual compiling pass, the information is remembered during the pre-compile      actual compiling pass, the information is remembered during the pre-compile
574      pass (on the stack unless there are more than 20 named groups, in which      pass (on the stack unless there are more than 20 named groups, in which
575      case malloc() is used) and the whole table is created before the actual      case malloc() is used) and the whole table is created before the actual
576      compile happens. This has simplified the code (it is now nearly 150 lines      compile happens. This has simplified the code (it is now nearly 150 lines
577      shorter) and prepared the way for better handling of references to groups      shorter) and prepared the way for better handling of references to groups
578      with duplicate names.      with duplicate names.
579    
580  15. A back reference to a named subpattern when there is more than one of the  15. A back reference to a named subpattern when there is more than one of the
581      same name now checks them in the order in which they appear in the pattern.      same name now checks them in the order in which they appear in the pattern.
582      The first one that is set is used for the reference. Previously only the      The first one that is set is used for the reference. Previously only the
583      first one was inspected. This change makes PCRE more compatible with Perl.      first one was inspected. This change makes PCRE more compatible with Perl.
584    
585  16. Unicode character properties were updated from Unicode 6.3.0.  16. Unicode character properties were updated from Unicode 6.3.0.
586    
587  17. The compile-time code for auto-possessification has been refactored, based  17. The compile-time code for auto-possessification has been refactored, based
588      on a patch by Zoltan Herczeg. It now happens after instead of during      on a patch by Zoltan Herczeg. It now happens after instead of during
589      compilation. The code is cleaner, and more cases are handled. The option      compilation. The code is cleaner, and more cases are handled. The option
590      PCRE_NO_AUTO_POSSESSIFY is added for testing purposes, and the -O and /O      PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
591      options in pcretest are provided to set it.      options in pcretest are provided to set it. It can also be set by
592        (*NO_AUTO_POSSESS) at the start of a pattern.
593  18. The character VT has been added to the set of characters that match \s and  
594      are generally treated as white space, following this same change in Perl  18. The character VT has been added to the default ("C" locale) set of
595      5.18. There is now no difference between "Perl space" and "POSIX space".      characters that match \s and are generally treated as white space,
596        following this same change in Perl 5.18. There is now no difference between
597  19. The code for checking named groups as conditions, either for being set or      "Perl space" and "POSIX space". Whether VT is treated as white space in
598        other locales depends on the locale.
599    
600    19. The code for checking named groups as conditions, either for being set or
601      for being recursed, has been refactored (this is related to 14 and 15      for being recursed, has been refactored (this is related to 14 and 15
602      above). Processing unduplicated named groups should now be as fast at      above). Processing unduplicated named groups should now be as fast at
603      numerical groups, and processing duplicated groups should be faster than      numerical groups, and processing duplicated groups should be faster than
604      before.      before.
605    
606  20. Two patches to the CMake build system, by Alexander Barkov:  20. Two patches to the CMake build system, by Alexander Barkov:
607    
608        (1) Replace the "source" command by "." in CMakeLists.txt because        (1) Replace the "source" command by "." in CMakeLists.txt because
609            "source" is a bash-ism.            "source" is a bash-ism.
610    
611        (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;        (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
612            without these the CMake build does not work on Solaris.            without these the CMake build does not work on Solaris.
613    
614  21. Perl has changed its handling of \8 and \9. If there is no previously  21. Perl has changed its handling of \8 and \9. If there is no previously
615      encountered capturing group of those numbers, they are treated as the      encountered capturing group of those numbers, they are treated as the
616      literal characters 8 and 9 instead of a binary zero followed by the      literal characters 8 and 9 instead of a binary zero followed by the
617      literals. PCRE now does the same.      literals. PCRE now does the same.
618    
619  22. Following Perl, added \o{} to specify codepoints in octal, making it  22. Following Perl, added \o{} to specify codepoints in octal, making it
620      possible to specify values greater than 0777 and also making them      possible to specify values greater than 0777 and also making them
621      unambiguous.      unambiguous.
622    
623  23. Perl now gives an error for missing closing braces after \x{... instead of  23. Perl now gives an error for missing closing braces after \x{... instead of
624      treating the string as literal. PCRE now does the same.      treating the string as literal. PCRE now does the same.
625    
626  24. RunTest used to grumble if an inappropriate test was selected explicitly,  24. RunTest used to grumble if an inappropriate test was selected explicitly,
627      but just skip it when running all tests. This make it awkward to run ranges      but just skip it when running all tests. This make it awkward to run ranges
628      of tests when one of them was inappropriate. Now it just skips any      of tests when one of them was inappropriate. Now it just skips any
629      inappropriate tests, as it always did when running all tests.      inappropriate tests, as it always did when running all tests.
630    
631  25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained  25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
632      character types such as \d or \w, too many callouts were inserted, and the      character types such as \d or \w, too many callouts were inserted, and the
633      data that they returned was rubbish.      data that they returned was rubbish.
634    
635  26. In UCP mode, \s was not matching two of the characters that Perl matches,  26. In UCP mode, \s was not matching two of the characters that Perl matches,
636      namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they      namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
637      were matched by \h. The code has now been refactored so that the lists of      were matched by \h. The code has now been refactored so that the lists of
638      the horizontal and vertical whitespace characters used for \h and \v (which      the horizontal and vertical whitespace characters used for \h and \v (which
639      are defined only in one place) are now also used for \s.      are defined only in one place) are now also used for \s.
640    
641  27. Add JIT support for the 64 bit TileGX architecture.  27. Add JIT support for the 64 bit TileGX architecture.
642      Patch by Jiong Wang (Tilera Corporation).      Patch by Jiong Wang (Tilera Corporation).
643    
644  28. Possessive quantifiers for classes (both explicit and automatically  28. Possessive quantifiers for classes (both explicit and automatically
645      generated) now use special opcodes instead of wrapping in ONCE brackets.      generated) now use special opcodes instead of wrapping in ONCE brackets.
646    
647  29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier  29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
648      (because it's meaningless), this was not happening when PCRE_CASELESS was      (because it's meaningless), this was not happening when PCRE_CASELESS was
649      set. Not wrong, but inefficient.      set. Not wrong, but inefficient.
650    
651  30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode  30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
652      properties for \w, \d, etc) is present in a test regex. Otherwise if the      properties for \w, \d, etc) is present in a test regex. Otherwise if the
653      test contains no characters greater than 255, Perl doesn't realise it      test contains no characters greater than 255, Perl doesn't realise it
654      should be using Unicode semantics.      should be using Unicode semantics.
655    
656  31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and  31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
657      [:punct:] when PCRE_UCP is set so as to include the same characters as Perl      [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
658      does in Unicode mode.      does in Unicode mode.
659    
660  32. Added the "forbid" facility to pcretest so that putting tests into the  32. Added the "forbid" facility to pcretest so that putting tests into the
661      wrong test files can sometimes be quickly detected.      wrong test files can sometimes be quickly detected.
662    
663  33. There is now a limit (default 250) on the depth of nesting of parentheses.  33. There is now a limit (default 250) on the depth of nesting of parentheses.
664      This limit is imposed to control the amount of system stack used at compile      This limit is imposed to control the amount of system stack used at compile
665      time. It can be changed at build time by --with-parens-nest-limit=xxx or      time. It can be changed at build time by --with-parens-nest-limit=xxx or
666      the equivalent in CMake.      the equivalent in CMake.
667    
668  34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time  34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
669      errors. Perl warns for these when in warning mode, but PCRE has no facility      errors. Perl warns for these when in warning mode, but PCRE has no facility
670      for giving warnings.      for giving warnings.
671    
672  35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.  35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
673      However, this was not working for (?!) because it is optimized to (*FAIL),      However, this was not working for (?!) because it is optimized to (*FAIL),
674      for which PCRE does not allow quantifiers. The optimization is now disabled      for which PCRE does not allow quantifiers. The optimization is now disabled
675      when a quantifier follows (?!). I can't see any use for this, but it makes      when a quantifier follows (?!). I can't see any use for this, but it makes
676      things uniform.      things uniform.
677    
678  36. Perl no longer allows group names to start with digits, so I have made this  36. Perl no longer allows group names to start with digits, so I have made this
679      change also in PCRE. It simplifies the code a bit.      change also in PCRE. It simplifies the code a bit.
680    
681    37. In extended mode, Perl ignores spaces before a + that indicates a
682        possessive quantifier. PCRE allowed a space before the quantifier, but not
683        before the possessive +. It now does.
684    
685    38. The use of \K (reset reported match start) within a repeated possessive
686        group such as (a\Kb)*+ was not working.
687    
688    40. Document that the same character tables must be used at compile time and
689        run time, and that the facility to pass tables to pcre_exec() and
690        pcre_dfa_exec() is for use only with saved/restored patterns.
691    
692    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
693        features for Builds with MSVC:
694    
695        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
696           builds). The .rc files can be used to set FileDescription and many other
697           attributes.
698    
699        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
700           This allows higher-level build scripts which want .pdb files to avoid
701           hard-coding the exact files needed."
702    
703    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
704        mean "start of word" and "end of word", respectively, as a transition aid.
705    
706    43. A minimizing repeat of a class containing codepoints greater than 255 in
707        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
708        compiled to use the heap for recursion.
709    
710    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
711        is configured.
712    
713    
714  Version 8.33 28-May-2013  Version 8.33 28-May-2013

Legend:
Removed from v.1394  
changed lines
  Added in v.1588

  ViewVC Help
Powered by ViewVC 1.1.5