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

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

  ViewVC Help
Powered by ViewVC 1.1.5