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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1322  
changed lines
  Added in v.1545

  ViewVC Help
Powered by ViewVC 1.1.5