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

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

  ViewVC Help
Powered by ViewVC 1.1.5