ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 751 by ph10, Fri Nov 18 11:13:30 2011 UTC revision 1485 by ph10, Wed Jun 18 16:31:32 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.21  Version 8.36 xx-xxx-2014
5  ------------  ------------------------
7    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
8        -Wmissing-field-initializers and -Wunused-parameter.
10    2.  The tests for quantifiers being too big (greater than 65535) were being
11        applied after reading the number, and stupidly assuming that integer
12        overflow would give a negative number. The tests are now applied as the
13        numbers are read.
15    3.  Tidy code in pcre_exec.c where two branches that used to be different are
16        now the same.
18    4.  The JIT compiler did not generate match limit checks for certain
19        bracketed expressions with quantifiers. This may lead to exponential
20        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
21        issue should be resolved now.
23    5.  Fixed an issue, which occures when nested alternatives are optimized
24        with table jumps.
26    6.  Inserted two casts and changed some ints to size_t in the light of some
27        reported 64-bit compiler warnings (Bugzilla 1477).
29    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
30        an empty string, which sometimes were behaving incorrectly in the
31        interpreter (though correctly in the JIT matcher). This pcretest input is
32        an example:
34          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
37        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
38        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
39        for an empty string was breaking the inner loop and carrying on at a lower
40        level, when possessive repeated groups should always return to a higher
41        level as they have no backtrack points in them. The empty string test now
42        occurs at the outer level.
44    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
45        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
47    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
48        doesn't).
50    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
51        to hold a pattern to be incorrectly computed (too small) when there were
52        named back references to duplicated names. This could cause "internal
53        error: code overflow" or "double free or corruption" or other memory
54        handling errors.
56    11. When named subpatterns had the same prefixes, back references could be
57        confused. For example, in this pattern:
59          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
61        the reference to 'Name' was incorrectly treated as a reference to a
62        duplicate name.
64    12. A pattern such as /^s?c/mi8 where the optional character has more than
65        one "other case" was incorrectly compiled such that it would only try to
66        match starting at "c".
69    Version 8.35 04-April-2014
70    --------------------------
72    1.  A new flag is set, when property checks are present in an XCLASS.
73        When this flag is not set, PCRE can perform certain optimizations
74        such as studying these XCLASS-es.
76    2.  The auto-possessification of character sets were improved: a normal
77        and an extended character set can be compared now. Furthermore
78        the JIT compiler optimizes more character set checks.
80    3.  Got rid of some compiler warnings for potentially uninitialized variables
81        that show up only when compiled with -O2.
83    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
84        of a match later then the end of the match. The pcretest program was not
85        handling the case sensibly - it was outputting from the start to the next
86        binary zero. It now reports this situation in a message, and outputs the
87        text from the end to the start.
89    5.  Fast forward search is improved in JIT. Instead of the first three
90        characters, any three characters with fixed position can be searched.
91        Search order: first, last, middle.
93    6.  Improve character range checks in JIT. Characters are read by an inprecise
94        function now, which returns with an unknown value if the character code is
95        above a certain treshold (e.g: 256). The only limitation is that the value
96        must be bigger than the treshold as well. This function is useful, when
97        the characters above the treshold are handled in the same way.
99    7.  The macros whose names start with RAWUCHAR are placeholders for a future
100        mode in which only the bottom 21 bits of 32-bit data items are used. To
101        make this more memorable for those maintaining the code, the names have
102        been changed to start with UCHAR21, and an extensive comment has been added
103        to their definition.
105    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
106        to the export list in Makefile.am (they were accidentally omitted from the
107        8.34 tarball).
109    9.  The informational output from pcretest used the phrase "starting byte set"
110        which is inappropriate for the 16-bit and 32-bit libraries. As the output
111        for "first char" and "need char" really means "non-UTF-char", I've changed
112        "byte" to "char", and slightly reworded the output. The documentation about
113        these values has also been (I hope) clarified.
115    10. Another JIT related optimization: use table jumps for selecting the correct
116        backtracking path, when more than four alternatives are present inside a
117        bracket.
119    11. Empty match is not possible, when the minimum length is greater than zero,
120        and there is no \K in the pattern. JIT should avoid empty match checks in
121        such cases.
123    12. In a caseless character class with UCP support, when a character with more
124        than one alternative case was not the first character of a range, not all
125        the alternative cases were added to the class. For example, s and \x{17f}
126        are both alternative cases for S: the class [RST] was handled correctly,
127        but [R-T] was not.
129    13. The configure.ac file always checked for pthread support when JIT was
130        enabled. This is not used in Windows, so I have put this test inside a
131        check for the presence of windows.h (which was already tested for).
133    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
134        The algorithm provides a way to skip certain starting offsets, and usually
135        faster than linear prefix searches.
137    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
138        as for 'fr_FR' and 'french'. For some reason, however, it then used the
139        Windows-specific input and output files, which have 'french' screwed in.
140        So this could never have worked. One of the problems with locales is that
141        they aren't always the same. I have now updated RunTest so that it checks
142        the output of the locale test (test 3) against three different output
143        files, and it allows the test to pass if any one of them matches. With luck
144        this should make the test pass on some versions of Solaris where it was
145        failing. Because of the uncertainty, the script did not used to stop if
146        test 3 failed; it now does. If further versions of a French locale ever
147        come to light, they can now easily be added.
149    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
150        there was a message during ./configure, but it did not stop. This now
151        provokes an error. The invalid example in README has been corrected.
152        If a value less than the minimum is given, the minimum value has always
153        been used, but now a warning is given.
155    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
156        was a bug in the test system, which is now fixed. Also, the list of various
157        configurations that are tested for each release did not have one with both
158        16/32 bits and --enable-bar-anycrlf. It now does.
160    18. pcretest was missing "-C bsr" for displaying the \R default setting.
162    19. Little endian PowerPC systems are supported now by the JIT compiler.
164    20. The fast forward newline mechanism could enter to an infinite loop on
165        certain invalid UTF-8 input. Although we don't support these cases
166        this issue can be fixed by a performance optimization.
168    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
169        not take account if existing stack usage. There is now a new global
170        variable called pcre_stack_guard that can be set to point to an external
171        function to check stack availability. It is called at the start of
172        processing every parenthesized group.
174    22. A typo in the code meant that in ungreedy mode the max/min qualifier
175        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
176        not match "ab".
178    23. When UTF was disabled, the JIT program reported some incorrect compile
179        errors. These messages are silenced now.
181    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
182        compiler.
184    25. Change all the temporary files used in RunGrepTest to be different to those
185        used by RunTest so that the tests can be run simultaneously, for example by
186        "make -j check".
189    Version 8.34 15-December-2013
190    -----------------------------
192    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
193        executable memory. Patch inspired by Carsten Klein.
195    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
196        this macro is never tested and has no effect, because the work to support
197        coverage involves only compiling and linking options and special targets in
198        the Makefile. The comment in config.h implied that defining the macro would
199        enable coverage support, which is totally false. There was also support for
200        setting this macro in the CMake files (my fault, I just copied it from
201        configure). SUPPORT_GCOV has now been removed.
203    3.  Make a small performance improvement in strlen16() and strlen32() in
204        pcretest.
206    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
207        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
208        these cases). There was also one in pcretest.c.
210    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
212    6.  In UTF mode, the code for checking whether a group could match an empty
213        string (which is used for indefinitely repeated groups to allow for
214        breaking an infinite loop) was broken when the group contained a repeated
215        negated single-character class with a character that occupied more than one
216        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
217        UTF-8 mode). The effect was undefined: the group might or might not be
218        deemed as matching an empty string, or the program might have crashed.
220    7.  The code for checking whether a group could match an empty string was not
221        recognizing that \h, \H, \v, \V, and \R must match a character.
223    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
224        an empty string. If it can, pcretest shows this in its information output.
226    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
227        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
228        matched by pcre_exec() without using JIT:
230        (a) If the rest of the pattern did not match after a maximal run of
231            grapheme clusters, the code for backing up to try with fewer of them
232            did not always back up over a full grapheme when characters that do not
233            have the modifier quality were involved, e.g. Hangul syllables.
235        (b) If the match point in a subject started with modifier character, and
236            there was no match, the code could incorrectly back up beyond the match
237            point, and potentially beyond the first character in the subject,
238            leading to a segfault or an incorrect match result.
240    10. A conditional group with an assertion condition could lead to PCRE
241        recording an incorrect first data item for a match if no other first data
242        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
243        first data item, and therefore matched "ca" after "c" instead of at the
244        start.
246    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
247        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
249    12. The source of pcregrep now includes z/OS-specific code so that it can be
250        compiled for z/OS as part of the special z/OS distribution.
252    13. Added the -T and -TM options to pcretest.
254    14. The code in pcre_compile.c for creating the table of named capturing groups
255        has been refactored. Instead of creating the table dynamically during the
256        actual compiling pass, the information is remembered during the pre-compile
257        pass (on the stack unless there are more than 20 named groups, in which
258        case malloc() is used) and the whole table is created before the actual
259        compile happens. This has simplified the code (it is now nearly 150 lines
260        shorter) and prepared the way for better handling of references to groups
261        with duplicate names.
263    15. A back reference to a named subpattern when there is more than one of the
264        same name now checks them in the order in which they appear in the pattern.
265        The first one that is set is used for the reference. Previously only the
266        first one was inspected. This change makes PCRE more compatible with Perl.
268    16. Unicode character properties were updated from Unicode 6.3.0.
270    17. The compile-time code for auto-possessification has been refactored, based
271        on a patch by Zoltan Herczeg. It now happens after instead of during
272        compilation. The code is cleaner, and more cases are handled. The option
273        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
274        options in pcretest are provided to set it. It can also be set by
275        (*NO_AUTO_POSSESS) at the start of a pattern.
277    18. The character VT has been added to the default ("C" locale) set of
278        characters that match \s and are generally treated as white space,
279        following this same change in Perl 5.18. There is now no difference between
280        "Perl space" and "POSIX space". Whether VT is treated as white space in
281        other locales depends on the locale.
283    19. The code for checking named groups as conditions, either for being set or
284        for being recursed, has been refactored (this is related to 14 and 15
285        above). Processing unduplicated named groups should now be as fast at
286        numerical groups, and processing duplicated groups should be faster than
287        before.
289    20. Two patches to the CMake build system, by Alexander Barkov:
291          (1) Replace the "source" command by "." in CMakeLists.txt because
292              "source" is a bash-ism.
294          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
295              without these the CMake build does not work on Solaris.
297    21. Perl has changed its handling of \8 and \9. If there is no previously
298        encountered capturing group of those numbers, they are treated as the
299        literal characters 8 and 9 instead of a binary zero followed by the
300        literals. PCRE now does the same.
302    22. Following Perl, added \o{} to specify codepoints in octal, making it
303        possible to specify values greater than 0777 and also making them
304        unambiguous.
306    23. Perl now gives an error for missing closing braces after \x{... instead of
307        treating the string as literal. PCRE now does the same.
309    24. RunTest used to grumble if an inappropriate test was selected explicitly,
310        but just skip it when running all tests. This make it awkward to run ranges
311        of tests when one of them was inappropriate. Now it just skips any
312        inappropriate tests, as it always did when running all tests.
314    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
315        character types such as \d or \w, too many callouts were inserted, and the
316        data that they returned was rubbish.
318    26. In UCP mode, \s was not matching two of the characters that Perl matches,
319        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
320        were matched by \h. The code has now been refactored so that the lists of
321        the horizontal and vertical whitespace characters used for \h and \v (which
322        are defined only in one place) are now also used for \s.
324    27. Add JIT support for the 64 bit TileGX architecture.
325        Patch by Jiong Wang (Tilera Corporation).
327    28. Possessive quantifiers for classes (both explicit and automatically
328        generated) now use special opcodes instead of wrapping in ONCE brackets.
330    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
331        (because it's meaningless), this was not happening when PCRE_CASELESS was
332        set. Not wrong, but inefficient.
334    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
335        properties for \w, \d, etc) is present in a test regex. Otherwise if the
336        test contains no characters greater than 255, Perl doesn't realise it
337        should be using Unicode semantics.
339    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
340        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
341        does in Unicode mode.
343    32. Added the "forbid" facility to pcretest so that putting tests into the
344        wrong test files can sometimes be quickly detected.
346    33. There is now a limit (default 250) on the depth of nesting of parentheses.
347        This limit is imposed to control the amount of system stack used at compile
348        time. It can be changed at build time by --with-parens-nest-limit=xxx or
349        the equivalent in CMake.
351    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
352        errors. Perl warns for these when in warning mode, but PCRE has no facility
353        for giving warnings.
355    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
356        However, this was not working for (?!) because it is optimized to (*FAIL),
357        for which PCRE does not allow quantifiers. The optimization is now disabled
358        when a quantifier follows (?!). I can't see any use for this, but it makes
359        things uniform.
361    36. Perl no longer allows group names to start with digits, so I have made this
362        change also in PCRE. It simplifies the code a bit.
364    37. In extended mode, Perl ignores spaces before a + that indicates a
365        possessive quantifier. PCRE allowed a space before the quantifier, but not
366        before the possessive +. It now does.
368    38. The use of \K (reset reported match start) within a repeated possessive
369        group such as (a\Kb)*+ was not working.
371    40. Document that the same character tables must be used at compile time and
372        run time, and that the facility to pass tables to pcre_exec() and
373        pcre_dfa_exec() is for use only with saved/restored patterns.
375    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
376        features for Builds with MSVC:
378        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
379           builds). The .rc files can be used to set FileDescription and many other
380           attributes.
382        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
383           This allows higher-level build scripts which want .pdb files to avoid
384           hard-coding the exact files needed."
386    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
387        mean "start of word" and "end of word", respectively, as a transition aid.
389    43. A minimizing repeat of a class containing codepoints greater than 255 in
390        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
391        compiled to use the heap for recursion.
393    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
394        is configured.
397    Version 8.33 28-May-2013
398    ------------------------
400    1.  Added 'U' to some constants that are compared to unsigned integers, to
401        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
402        variables that are added to signed variables, to ensure the result is
403        signed and can be negated.
405    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
406        CMake config files.
408    3.  Revise the creation of config.h.generic so that all boolean macros are
409        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
410        overriding via -D on the command line possible.
412    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
413        to unsigned int is reported to make a quite noticeable speed difference in
414        a specific Windows environment. Testing on Linux did also appear to show
415        some benefit (and it is clearly not harmful). Also fixed the definition of
416        Xop which should be unsigned.
418    5.  Related to (4), changing the definition of the intermediate variable cc
419        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
420        improvements.
422    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
423        unnecessary spaces.
425    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
426        and later.
428    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
430    9.  Optimizing fast_forward_start_bits in JIT.
432    10. Adding support for callouts in JIT, and fixing some issues revealed
433        during this work. Namely:
435        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
437        (b) Minimum length was not checked before the matching is started.
439    11. The value of capture_last that is passed to callouts was incorrect in some
440        cases when there was a capture on one path that was subsequently abandoned
441        after a backtrack. Also, the capture_last value is now reset after a
442        recursion, since all captures are also reset in this case.
444    12. The interpreter no longer returns the "too many substrings" error in the
445        case when an overflowing capture is in a branch that is subsequently
446        abandoned after a backtrack.
448    13. In the pathological case when an offset vector of size 2 is used, pcretest
449        now prints out the matched string after a yield of 0 or 1.
451    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
452        Only supported by the JIT compiler at the moment.
454    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
456    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
457        offset of the starting point of the matching process, provided the offsets
458        vector is large enough.
460    17. The \A escape now records a lookbehind value of 1, though its execution
461        does not actually inspect the previous character. This is to ensure that,
462        in partial multi-segment matching, at least one character from the old
463        segment is retained when a new segment is processed. Otherwise, if there
464        are no lookbehinds in the pattern, \A might match incorrectly at the start
465        of a new segment.
467    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
469    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
470        gives some modest performance improvement in 8-bit mode.
472    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
473        be expressed in certain programming languages using Universal Character
474        Names.
476    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
477        which points out that "non characters" are not "characters that may not
478        appear in Unicode strings" but rather "characters that are reserved for
479        internal use and have only local meaning".
481    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
482        there was a conditional group that depended on an assertion, if the
483        assertion was false, the callout that immediately followed the alternation
484        in the condition was skipped when pcre_exec() was used for matching.
486    23. Allow an explicit callout to be inserted before an assertion that is the
487        condition for a conditional group, for compatibility with automatic
488        callouts, which always insert a callout at this point.
490    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
491        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
493    25. (*PRUNE) is now supported by the JIT compiler.
495    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
497    27. Fix the case where there are two or more SKIPs with arguments that may be
498        ignored.
500    28. (*SKIP) is now supported by the JIT compiler.
502    29. (*THEN) is now supported by the JIT compiler.
504    30. Update RunTest with additional test selector options.
506    31. The way PCRE handles backtracking verbs has been changed in two ways.
508        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
509        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
510        backtracking. In some cases this makes it more Perl-compatible, but Perl's
511        rather obscure rules do not always do the same thing.
513        (2) Previously, backtracking verbs were confined within assertions. This is
514        no longer the case for positive assertions, except for (*ACCEPT). Again,
515        this sometimes improves Perl compatibility, and sometimes does not.
517    32. A number of tests that were in test 2 because Perl did things differently
518        have been moved to test 1, because either Perl or PCRE has changed, and
519        these tests are now compatible.
521    32. Backtracking control verbs are now handled in the same way in JIT and
522        interpreter.
524    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
525        contained a forward subroutine reference caused a compile error.
527    34. Auto-detect and optimize limited repetitions in JIT.
529    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
530        blocking (*UTF) etc.
532    36. In the interpreter, maximizing pattern repetitions for characters and
533        character types now use tail recursion, which reduces stack usage.
535    37. The value of the max lookbehind was not correctly preserved if a compiled
536        and saved regex was reloaded on a host of different endianness.
538    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
539        of the compiled pattern block, expand the flags field from 16 to 32 bits
540        because it was almost full.
542    39. Try madvise first before posix_madvise.
544    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
545        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
546        original change locked out all matches of empty strings. This has been
547        changed so that one match of an empty string per line is recognized.
548        Subsequent searches on the same line (for colouring or for --only-matching,
549        for example) do not recognize empty strings.
551    41. Applied a user patch to fix a number of spelling mistakes in comments.
553    42. Data lines longer than 65536 caused pcretest to crash.
555    43. Clarified the data type for length and startoffset arguments for pcre_exec
556        and pcre_dfa_exec in the function-specific man pages, where they were
557        explicitly stated to be in bytes, never having been updated. I also added
558        some clarification to the pcreapi man page.
560    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
561        a segmentation fault.
564    Version 8.32 30-November-2012
565    -----------------------------
567    1.  Improved JIT compiler optimizations for first character search and single
568        character iterators.
570    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
571        Patch by Daniel Richard G.
573    3.  Single character iterator optimizations in the JIT compiler.
575    4.  Improved JIT compiler optimizations for character ranges.
577    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
578        Reported by Giuseppe D'Angelo.
580    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
581        of a line, was being set incorrectly in cases where .* appeared inside
582        atomic brackets at the start of a pattern, or where there was a subsequent
583        *PRUNE or *SKIP.
585    7.  Improved instruction cache flush for POWER/PowerPC.
586        Patch by Daniel Richard G.
588    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
589        grep:
591        (a) There is now no limit to the number of patterns to be matched.
593        (b) An error is given if a pattern is too long.
595        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
596            are now supported.
598        (d) --exclude-from and --include-from (multiple use) have been added.
600        (e) Exclusions and inclusions now apply to all files and directories, not
601            just to those obtained from scanning a directory recursively.
603        (f) Multiple uses of -f and --file-list are now supported.
605        (g) In a Windows environment, the default for -d has been changed from
606            "read" (the GNU grep default) to "skip", because otherwise the presence
607            of a directory in the file list provokes an error.
609        (h) The documentation has been revised and clarified in places.
611    9.  Improve the matching speed of capturing brackets.
613    10. Changed the meaning of \X so that it now matches a Unicode extended
614        grapheme cluster.
616    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
617        out POSIX threads when JIT support is configured.
619    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
621    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
622        structure could go wrong in environments where size_t is not the same size
623        as int.
625    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
626        set.
628    15. The EBCDIC support had decayed; later updates to the code had included
629        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
630        general tidy up of EBCDIC-related issues, and the documentation was also
631        not quite right. There is now a test that can be run on ASCII systems to
632        check some of the EBCDIC-related things (but is it not a full test).
634    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
635        in a small tidy to the code.
637    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
639    18. If the --only-matching (-o) option in pcregrep is specified multiple
640        times, each one causes appropriate output. For example, -o1 -o2 outputs the
641        substrings matched by the 1st and 2nd capturing parentheses. A separating
642        string can be specified by --om-separator (default empty).
644    19. Improving the first n character searches.
646    20. Turn case lists for horizontal and vertical white space into macros so that
647        they are defined only once.
649    21. This set of changes together give more compatible Unicode case-folding
650        behaviour for characters that have more than one other case when UCP
651        support is available.
653        (a) The Unicode property table now has offsets into a new table of sets of
654            three or more characters that are case-equivalent. The MultiStage2.py
655            script that generates these tables (the pcre_ucd.c file) now scans
656            CaseFolding.txt instead of UnicodeData.txt for character case
657            information.
659        (b) The code for adding characters or ranges of characters to a character
660            class has been abstracted into a generalized function that also handles
661            case-independence. In UTF-mode with UCP support, this uses the new data
662            to handle characters with more than one other case.
664        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
665            whose other case is greater than 256 are now correctly matched
666            caselessly. Previously, the high codepoint matched the low one, but not
667            vice versa.
669        (d) The processing of \h, \H, \v, and \ in character classes now makes use
670            of the new class addition function, using character lists defined as
671            macros alongside the case definitions of 20 above.
673        (e) Caseless back references now work with characters that have more than
674            one other case.
676        (f) General caseless matching of characters with more than one other case
677            is supported.
679    22. Unicode character properties were updated from Unicode 6.2.0
681    23. Improved CMake support under Windows. Patch by Daniel Richard G.
683    24. Add support for 32-bit character strings, and UTF-32
685    25. Major JIT compiler update (code refactoring and bugfixing).
686        Experimental Sparc 32 support is added.
688    26. Applied a modified version of Daniel Richard G's patch to create
689        pcre.h.generic and config.h.generic by "make" instead of in the
690        PrepareRelease script.
692    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
693        pcre_compile.c when checking for a zero character.
695    28. Introducing a native interface for JIT. Through this interface, the compiled
696        machine code can be directly executed. The purpose of this interface is to
697        provide fast pattern matching, so several sanity checks are not performed.
698        However, feature tests are still performed. The new interface provides
699        1.4x speedup compared to the old one.
701    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
702        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
703        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
705    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
706        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
707        the "old" RFC 2279). Instead, it ended up passing a negative length to
708        pcre_exec().
710    31. Add support for GCC's visibility feature to hide internal functions.
712    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
713        "unknown -C option" after outputting 0 or 1.
715    33. There is now support for generating a code coverage report for the test
716        suite in environments where gcc is the compiler and lcov is installed. This
717        is mainly for the benefit of the developers.
719    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
720        unaddressable using valgrind annotations, allowing valgrind to detect
721        invalid memory accesses. This is mainly for the benefit of the developers.
723    25. (*UTF) can now be used to start a pattern in any of the three libraries.
725    26. Give configure error if --enable-cpp but no C++ compiler found.
728    Version 8.31 06-July-2012
729    -------------------------
731    1.  Fixing a wrong JIT test case and some compiler warnings.
733    2.  Removed a bashism from the RunTest script.
735    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
736        to unsigned type, result still unsigned" that was given by an MS compiler
737        on encountering the code "-sizeof(xxx)".
739    4.  Partial matching support is added to the JIT compiler.
741    5.  Fixed several bugs concerned with partial matching of items that consist
742        of more than one character:
744        (a) /^(..)\1/ did not partially match "aba" because checking references was
745            done on an "all or nothing" basis. This also applied to repeated
746            references.
748        (b) \R did not give a hard partial match if \r was found at the end of the
749            subject.
751        (c) \X did not give a hard partial match after matching one or more
752            characters at the end of the subject.
754        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
755            a partial match for the string "\r".
757        (e) When newline was set to CRLF, the metacharacter "." did not recognize
758            a partial match for a CR character at the end of the subject string.
760    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
761        running pcretest, the text "(JIT)" added to the output whenever JIT is
762        actually used to run the match.
764    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
765        or /S+[+] with a digit between 1 and 7.
767    8.  OP_NOT now supports any UTF character not just single-byte ones.
769    9.  (*MARK) control verb is now supported by the JIT compiler.
771    10. The command "./RunTest list" lists the available tests without actually
772        running any of them. (Because I keep forgetting what they all are.)
776    12. Applied a (slightly modified) user-supplied patch that improves performance
777        when the heap is used for recursion (compiled with --disable-stack-for-
778        recursion). Instead of malloc and free for each heap frame each time a
779        logical recursion happens, frames are retained on a chain and re-used where
780        possible. This sometimes gives as much as 30% improvement.
782    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
783        call.
785    14. As documented, (*COMMIT) is now confined to within a positive assertion.
787    15. It is now possible to link pcretest with libedit as an alternative to
788        libreadline.
790    16. (*COMMIT) control verb is now supported by the JIT compiler.
792    17. The Unicode data tables have been updated to Unicode 6.1.0.
794    18. Added --file-list option to pcregrep.
796    19. Added binary file support to pcregrep, including the -a, --binary-files,
797        -I, and --text options.
799    20. The madvise function is renamed for posix_madvise for QNX compatibility
800        reasons. Fixed by Giuseppe D'Angelo.
802    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
804    22. Changed the option for creating symbolic links for 16-bit man pages from
805        -s to -sf so that re-installing does not cause issues.
807    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
809    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
810        matches in certain environments (the workspace was not being correctly
811        retained). Also added to pcre_dfa_exec() a simple plausibility check on
812        some of the workspace data at the beginning of a restart.
814    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
815        was not doing so when it should - probably a typo introduced by SVN 528
816        (change 8.10/14).
818    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
819        \w+ when the character tables indicated that \x{c4} was a word character.
820        There were several related cases, all because the tests for doing a table
821        lookup were testing for characters less than 127 instead of 255.
823    27. If a pattern contains capturing parentheses that are not used in a match,
824        their slots in the ovector are set to -1. For those that are higher than
825        any matched groups, this happens at the end of processing. In the case when
826        there were back references that the ovector was too small to contain
827        (causing temporary malloc'd memory to be used during matching), and the
828        highest capturing number was not used, memory off the end of the ovector
829        was incorrectly being set to -1. (It was using the size of the temporary
830        memory instead of the true size.)
832    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
833        ovector size, it uses memory at the end of the block that it has got.
835    29. Check for an overlong MARK name and give an error at compile time. The
836        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
838    30. JIT compiler update.
840    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
841        Rill for the patch.
843    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
845    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
847    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
848        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
849        was enabled.
851    35. Improve JIT code generation for greedy plus quantifier.
853    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
854        1 to "aa" instead of to an empty string. The bug affected repeated groups
855        that could potentially match an empty string.
857    37. Optimizing single character iterators in JIT.
859    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
860        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
861        codepoints that are too big for the mode are faulted, and in a UTF mode,
862        disallowed codepoints are also faulted.
864    39. If PCRE was compiled with UTF support, in three places in the DFA
865        matcher there was code that should only have been obeyed in UTF mode, but
866        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
867        processing when bytes with values greater than 127 were present. In 16-bit
868        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
869        both cases the values are those that cannot be the first data item in a UTF
870        character. The three items that might have provoked this were recursions,
871        possessively repeated groups, and atomic groups.
873    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
874        and pcregrep, because some OS require shared objects to be explicitly
875        passed to ld, causing the link step to fail if they are not.
877    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
878        mode, patterns that started with \h* or \R* might be incorrectly matched.
881    Version 8.30 04-February-2012
882    -----------------------------
884    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
885        name is defined in ctype.h.
887    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
888        only in quite long subpatterns.
890    3.  Removed the function pcre_info(), which has been obsolete and deprecated
891        since it was replaced by pcre_fullinfo() in February 2000.
893    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
894        match a (*MARK), and the match failed at the start of the subject, a
895        reference to memory before the start of the subject could occur. This bug
896        was introduced by fix 17 of release 8.21.
898    5.  A reference to an unset group with zero minimum repetition was giving
899        totally wrong answers (in non-JavaScript-compatibility mode). For example,
900        /(another)?(\1?)test/ matched against "hello world test". This bug was
901        introduced in release 8.13.
903    6.  Add support for 16-bit character strings (a large amount of work involving
904        many changes and refactorings).
906    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
907        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
908        from a file.
910    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
911        rounding is not applied in this particular case).
913    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
914        if they appear, or are escaped, in patterns.
916    10. Get rid of a number of -Wunused-but-set-variable warnings.
918    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
919        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
920        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
921        also returns the mark "x". This bug applied to capturing parentheses,
922        non-capturing parentheses, and atomic parentheses. It also applied to some
923        assertions.
925    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
926        information out of configure.ac instead of relying on pcre.h.generic, which
927        is not stored in the repository.
929    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
930        -lreadline.
932    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
934    15. Applied Graycode's patch to put the top-level frame on the stack rather
935        than the heap when not using the stack for recursion. This gives a
936        performance improvement in many cases when recursion is not deep.
938    16. Experimental code added to "pcretest -C" to output the stack frame size.
941    Version 8.21 12-Dec-2011
942    ------------------------
944  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
# Line 13  Version 8.21 Line 950  Version 8.21
950      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
951      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
953  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
954      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
955      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
# Line 22  Version 8.21 Line 959  Version 8.21
960  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
961      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
962      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
964  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
965      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
966      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)
967      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
968      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
969      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
970      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
971      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
972      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
974  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
975      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
977  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
978      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
979      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
980      the first (A) could occur when it should not.      the first (A) could occur when it should not.
982  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
984    11. JIT should use pcre_malloc/pcre_free for allocation.
986    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
987        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
988        is anything other than /usr, -L is still shown).
990    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
992    14. Perl does not support \N without a following name in a [] class; PCRE now
993        also gives an error.
995    15. If a forward reference was repeated with an upper limit of around 2000,
996        it caused the error "internal error: overran compiling workspace". The
997        maximum number of forward references (including repeats) was limited by the
998        internal workspace, and dependent on the LINK_SIZE. The code has been
999        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
1000        the default depends on LINK_SIZE. There is a new upper limit (for safety)
1001        of around 200,000 forward references. While doing this, I also speeded up
1002        the filling in of repeated forward references.
1004    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
1005        incorrectly expecting the subject to contain another "a" after the start.
1007    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
1008        in the match, the SKIP should be ignored. This was not happening; instead
1009        the SKIP was being treated as NOMATCH. For patterns such as
1010        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
1011        tested.
1013    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
1014        now much more compatible with Perl, in particular in cases where the result
1015        is a non-match for a non-anchored pattern. For example, if
1016        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
1017        "m", where previously it did not return a name. A side effect of this
1018        change is that for partial matches, the last encountered mark name is
1019        returned, as for non matches. A number of tests that were previously not
1020        Perl-compatible have been moved into the Perl-compatible test files. The
1021        refactoring has had the pleasing side effect of removing one argument from
1022        the match() function, thus reducing its stack requirements.
1024    19. If the /S+ option was used in pcretest to study a pattern using JIT,
1025        subsequent uses of /S (without +) incorrectly behaved like /S+.
1027    21. Retrieve executable code size support for the JIT compiler and fixing
1028        some warnings.
1030    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
1031        not work when the shorter character appeared right at the end of the
1032        subject string.
1034    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
1035        systems.
1037    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
1038        output it when the /M option is used in pcretest.
1040    25. The CheckMan script was not being included in the distribution. Also, added
1041        an explicit "perl" to run Perl scripts from the PrepareRelease script
1042        because this is reportedly needed in Windows.
1044    26. If study data was being save in a file and studying had not found a set of
1045        "starts with" bytes for the pattern, the data written to the file (though
1046        never used) was taken from uninitialized memory and so caused valgrind to
1047        complain.
1049    27. Updated RunTest.bat as provided by Sheri Pierce.
1051    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
1053    29. Computation of memory usage for the table of capturing group names was
1054        giving an unnecessarily large value.
1057  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
# Line 1059  Version 7.9 11-Apr-09 Line 2068  Version 7.9 11-Apr-09
2068  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
2069      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
2070      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2071      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2072        8.33.]
2074  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
2075      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 1302  Version 7.7 07-May-08 Line 2312  Version 7.7 07-May-08
2312      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2313      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2314      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2315      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2316      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2317      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.751  
changed lines
  Added in v.1485

  ViewVC Help
Powered by ViewVC 1.1.5