ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.753  
changed lines
  Added in v.1533

  ViewVC Help
Powered by ViewVC 1.1.5