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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.934  
changed lines
  Added in v.1586

  ViewVC Help
Powered by ViewVC 1.1.5