ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 934 by ph10, Sat Feb 25 12:30:36 2012 UTC revision 1462 by ph10, Mon Mar 10 16:28:54 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.31  Version 8.35-RC1 04-March-2014
5    ------------------------------
7    1.  A new flag is set, when property checks are present in an XCLASS.
8        When this flag is not set, PCRE can perform certain optimizations
9        such as studying these XCLASS-es.
11    2.  The auto-possessification of character sets were improved: a normal
12        and an extended character set can be compared now. Furthermore
13        the JIT compiler optimizes more character set checks.
15    3.  Got rid of some compiler warnings for potentially uninitialized variables
16        that show up only when compiled with -O2.
18    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
19        of a match later then the end of the match. The pcretest program was not
20        handling the case sensibly - it was outputting from the start to the next
21        binary zero. It now reports this situation in a message, and outputs the
22        text from the end to the start.
24    5.  Fast forward search is improved in JIT. Instead of the first three
25        characters, any three characters with fixed position can be searched.
26        Search order: first, last, middle.
28    6.  Improve character range checks in JIT. Characters are read by an inprecise
29        function now, which returns with an unknown value if the character code is
30        above a certain treshold (e.g: 256). The only limitation is that the value
31        must be bigger than the treshold as well. This function is useful, when
32        the characters above the treshold are handled in the same way.
34    7.  The macros whose names start with RAWUCHAR are placeholders for a future
35        mode in which only the bottom 21 bits of 32-bit data items are used. To
36        make this more memorable for those maintaining the code, the names have
37        been changed to start with UCHAR21, and an extensive comment has been added
38        to their definition.
40    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
41        to the export list in Makefile.am (they were accidentally omitted from the
42        8.34 tarball).
44    9.  The informational output from pcretest used the phrase "starting byte set"
45        which is inappropriate for the 16-bit and 32-bit libraries. As the output
46        for "first char" and "need char" really means "non-UTF-char", I've changed
47        "byte" to "char", and slightly reworded the output. The documentation about
48        these values has also been (I hope) clarified.
50    10. Another JIT related optimization: use table jumps for selecting the correct
51        backtracking path, when more than four alternatives are present inside a
52        bracket.
54    11. Empty match is not possible, when the minimum length is greater than zero,
55        and there is no \K in the pattern. JIT should avoid empty match checks in
56        such cases.
58    12. In a caseless character class with UCP support, when a character with more
59        than one alternative case was not the first character of a range, not all
60        the alternative cases were added to the class. For example, s and \x{17f}
61        are both alternative cases for S: the class [RST] was handled correctly,
62        but [R-T] was not.
64    13. The configure.ac file always checked for pthread support when JIT was
65        enabled. This is not used in Windows, so I have put this test inside a
66        check for the presence of windows.h (which was already tested for).
68    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
69        The algorithm provides a way to skip certain starting offsets, and usually
70        faster than linear prefix searches.
72    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
73        as for 'fr_FR' and 'french'. For some reason, however, it then used the
74        Windows-specific input and output files, which have 'french' screwed in.
75        So this could never have worked. One of the problems with locales is that
76        they aren't always the same. I have now updated RunTest so that it checks
77        the output of the locale test (test 3) against three different output
78        files, and it allows the test to pass if any one of them matches. With luck
79        this should make the test pass on some versions of Solaris where it was
80        failing. Because of the uncertainty, the script did not used to stop if
81        test 3 failed; it now does. If further versions of a French locale ever
82        come to light, they can now easily be added.
84    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
85        there was a message during ./configure, but it did not stop. This now
86        provokes an error. The invalid example in README has been corrected.
87        If a value less than the minimum is given, the minimum value has always
88        been used, but now a warning is given.
90    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
91        was a bug in the test system, which is now fixed. Also, the list of various
92        configurations that are tested for each release did not have one with both
93        16/32 bits and --enable-bar-anycrlf. It now does.
95    18. pcretest was missing "-C bsr" for displaying the \R default setting.
97    19. Little endian PowerPC systems are supported now by the JIT compiler.
99    20. The fast forward newline mechanism could enter to an infinite loop on
100        certain invalid UTF-8 input. Although we don't support these cases
101        this issue can be fixed by a performance optimization.
103    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
104        not take account if existing stack usage. There is now a new global
105        variable called pcre_stack_guard that can be set to point to an external
106        function to check stack availability. It is called at the start of
107        processing every parenthesized group.
109    22. A typo in the code meant that in ungreedy mode the max/min qualifier
110        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
111        not match "ab".
114    Version 8.34 15-December-2013
115  -----------------------------  -----------------------------
117    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
118        executable memory. Patch inspired by Carsten Klein.
120    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
121        this macro is never tested and has no effect, because the work to support
122        coverage involves only compiling and linking options and special targets in
123        the Makefile. The comment in config.h implied that defining the macro would
124        enable coverage support, which is totally false. There was also support for
125        setting this macro in the CMake files (my fault, I just copied it from
126        configure). SUPPORT_GCOV has now been removed.
128    3.  Make a small performance improvement in strlen16() and strlen32() in
129        pcretest.
131    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
132        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
133        these cases). There was also one in pcretest.c.
135    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
137    6.  In UTF mode, the code for checking whether a group could match an empty
138        string (which is used for indefinitely repeated groups to allow for
139        breaking an infinite loop) was broken when the group contained a repeated
140        negated single-character class with a character that occupied more than one
141        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
142        UTF-8 mode). The effect was undefined: the group might or might not be
143        deemed as matching an empty string, or the program might have crashed.
145    7.  The code for checking whether a group could match an empty string was not
146        recognizing that \h, \H, \v, \V, and \R must match a character.
148    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
149        an empty string. If it can, pcretest shows this in its information output.
151    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
152        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
153        matched by pcre_exec() without using JIT:
155        (a) If the rest of the pattern did not match after a maximal run of
156            grapheme clusters, the code for backing up to try with fewer of them
157            did not always back up over a full grapheme when characters that do not
158            have the modifier quality were involved, e.g. Hangul syllables.
160        (b) If the match point in a subject started with modifier character, and
161            there was no match, the code could incorrectly back up beyond the match
162            point, and potentially beyond the first character in the subject,
163            leading to a segfault or an incorrect match result.
165    10. A conditional group with an assertion condition could lead to PCRE
166        recording an incorrect first data item for a match if no other first data
167        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
168        first data item, and therefore matched "ca" after "c" instead of at the
169        start.
171    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
172        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
174    12. The source of pcregrep now includes z/OS-specific code so that it can be
175        compiled for z/OS as part of the special z/OS distribution.
177    13. Added the -T and -TM options to pcretest.
179    14. The code in pcre_compile.c for creating the table of named capturing groups
180        has been refactored. Instead of creating the table dynamically during the
181        actual compiling pass, the information is remembered during the pre-compile
182        pass (on the stack unless there are more than 20 named groups, in which
183        case malloc() is used) and the whole table is created before the actual
184        compile happens. This has simplified the code (it is now nearly 150 lines
185        shorter) and prepared the way for better handling of references to groups
186        with duplicate names.
188    15. A back reference to a named subpattern when there is more than one of the
189        same name now checks them in the order in which they appear in the pattern.
190        The first one that is set is used for the reference. Previously only the
191        first one was inspected. This change makes PCRE more compatible with Perl.
193    16. Unicode character properties were updated from Unicode 6.3.0.
195    17. The compile-time code for auto-possessification has been refactored, based
196        on a patch by Zoltan Herczeg. It now happens after instead of during
197        compilation. The code is cleaner, and more cases are handled. The option
198        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
199        options in pcretest are provided to set it. It can also be set by
200        (*NO_AUTO_POSSESS) at the start of a pattern.
202    18. The character VT has been added to the default ("C" locale) set of
203        characters that match \s and are generally treated as white space,
204        following this same change in Perl 5.18. There is now no difference between
205        "Perl space" and "POSIX space". Whether VT is treated as white space in
206        other locales depends on the locale.
208    19. The code for checking named groups as conditions, either for being set or
209        for being recursed, has been refactored (this is related to 14 and 15
210        above). Processing unduplicated named groups should now be as fast at
211        numerical groups, and processing duplicated groups should be faster than
212        before.
214    20. Two patches to the CMake build system, by Alexander Barkov:
216          (1) Replace the "source" command by "." in CMakeLists.txt because
217              "source" is a bash-ism.
219          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
220              without these the CMake build does not work on Solaris.
222    21. Perl has changed its handling of \8 and \9. If there is no previously
223        encountered capturing group of those numbers, they are treated as the
224        literal characters 8 and 9 instead of a binary zero followed by the
225        literals. PCRE now does the same.
227    22. Following Perl, added \o{} to specify codepoints in octal, making it
228        possible to specify values greater than 0777 and also making them
229        unambiguous.
231    23. Perl now gives an error for missing closing braces after \x{... instead of
232        treating the string as literal. PCRE now does the same.
234    24. RunTest used to grumble if an inappropriate test was selected explicitly,
235        but just skip it when running all tests. This make it awkward to run ranges
236        of tests when one of them was inappropriate. Now it just skips any
237        inappropriate tests, as it always did when running all tests.
239    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
240        character types such as \d or \w, too many callouts were inserted, and the
241        data that they returned was rubbish.
243    26. In UCP mode, \s was not matching two of the characters that Perl matches,
244        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
245        were matched by \h. The code has now been refactored so that the lists of
246        the horizontal and vertical whitespace characters used for \h and \v (which
247        are defined only in one place) are now also used for \s.
249    27. Add JIT support for the 64 bit TileGX architecture.
250        Patch by Jiong Wang (Tilera Corporation).
252    28. Possessive quantifiers for classes (both explicit and automatically
253        generated) now use special opcodes instead of wrapping in ONCE brackets.
255    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
256        (because it's meaningless), this was not happening when PCRE_CASELESS was
257        set. Not wrong, but inefficient.
259    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
260        properties for \w, \d, etc) is present in a test regex. Otherwise if the
261        test contains no characters greater than 255, Perl doesn't realise it
262        should be using Unicode semantics.
264    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
265        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
266        does in Unicode mode.
268    32. Added the "forbid" facility to pcretest so that putting tests into the
269        wrong test files can sometimes be quickly detected.
271    33. There is now a limit (default 250) on the depth of nesting of parentheses.
272        This limit is imposed to control the amount of system stack used at compile
273        time. It can be changed at build time by --with-parens-nest-limit=xxx or
274        the equivalent in CMake.
276    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
277        errors. Perl warns for these when in warning mode, but PCRE has no facility
278        for giving warnings.
280    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
281        However, this was not working for (?!) because it is optimized to (*FAIL),
282        for which PCRE does not allow quantifiers. The optimization is now disabled
283        when a quantifier follows (?!). I can't see any use for this, but it makes
284        things uniform.
286    36. Perl no longer allows group names to start with digits, so I have made this
287        change also in PCRE. It simplifies the code a bit.
289    37. In extended mode, Perl ignores spaces before a + that indicates a
290        possessive quantifier. PCRE allowed a space before the quantifier, but not
291        before the possessive +. It now does.
293    38. The use of \K (reset reported match start) within a repeated possessive
294        group such as (a\Kb)*+ was not working.
296    40. Document that the same character tables must be used at compile time and
297        run time, and that the facility to pass tables to pcre_exec() and
298        pcre_dfa_exec() is for use only with saved/restored patterns.
300    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
301        features for Builds with MSVC:
303        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
304           builds). The .rc files can be used to set FileDescription and many other
305           attributes.
307        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
308           This allows higher-level build scripts which want .pdb files to avoid
309           hard-coding the exact files needed."
311    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
312        mean "start of word" and "end of word", respectively, as a transition aid.
314    43. A minimizing repeat of a class containing codepoints greater than 255 in
315        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
316        compiled to use the heap for recursion.
318    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
319        is configured.
322    Version 8.33 28-May-2013
323    ------------------------
325    1.  Added 'U' to some constants that are compared to unsigned integers, to
326        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
327        variables that are added to signed variables, to ensure the result is
328        signed and can be negated.
330    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
331        CMake config files.
333    3.  Revise the creation of config.h.generic so that all boolean macros are
334        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
335        overriding via -D on the command line possible.
337    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
338        to unsigned int is reported to make a quite noticeable speed difference in
339        a specific Windows environment. Testing on Linux did also appear to show
340        some benefit (and it is clearly not harmful). Also fixed the definition of
341        Xop which should be unsigned.
343    5.  Related to (4), changing the definition of the intermediate variable cc
344        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
345        improvements.
347    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
348        unnecessary spaces.
350    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
351        and later.
353    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
355    9.  Optimizing fast_forward_start_bits in JIT.
357    10. Adding support for callouts in JIT, and fixing some issues revealed
358        during this work. Namely:
360        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
362        (b) Minimum length was not checked before the matching is started.
364    11. The value of capture_last that is passed to callouts was incorrect in some
365        cases when there was a capture on one path that was subsequently abandoned
366        after a backtrack. Also, the capture_last value is now reset after a
367        recursion, since all captures are also reset in this case.
369    12. The interpreter no longer returns the "too many substrings" error in the
370        case when an overflowing capture is in a branch that is subsequently
371        abandoned after a backtrack.
373    13. In the pathological case when an offset vector of size 2 is used, pcretest
374        now prints out the matched string after a yield of 0 or 1.
376    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
377        Only supported by the JIT compiler at the moment.
379    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
381    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
382        offset of the starting point of the matching process, provided the offsets
383        vector is large enough.
385    17. The \A escape now records a lookbehind value of 1, though its execution
386        does not actually inspect the previous character. This is to ensure that,
387        in partial multi-segment matching, at least one character from the old
388        segment is retained when a new segment is processed. Otherwise, if there
389        are no lookbehinds in the pattern, \A might match incorrectly at the start
390        of a new segment.
392    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
394    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
395        gives some modest performance improvement in 8-bit mode.
397    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
398        be expressed in certain programming languages using Universal Character
399        Names.
401    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
402        which points out that "non characters" are not "characters that may not
403        appear in Unicode strings" but rather "characters that are reserved for
404        internal use and have only local meaning".
406    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
407        there was a conditional group that depended on an assertion, if the
408        assertion was false, the callout that immediately followed the alternation
409        in the condition was skipped when pcre_exec() was used for matching.
411    23. Allow an explicit callout to be inserted before an assertion that is the
412        condition for a conditional group, for compatibility with automatic
413        callouts, which always insert a callout at this point.
415    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
416        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
418    25. (*PRUNE) is now supported by the JIT compiler.
420    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
422    27. Fix the case where there are two or more SKIPs with arguments that may be
423        ignored.
425    28. (*SKIP) is now supported by the JIT compiler.
427    29. (*THEN) is now supported by the JIT compiler.
429    30. Update RunTest with additional test selector options.
431    31. The way PCRE handles backtracking verbs has been changed in two ways.
433        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
434        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
435        backtracking. In some cases this makes it more Perl-compatible, but Perl's
436        rather obscure rules do not always do the same thing.
438        (2) Previously, backtracking verbs were confined within assertions. This is
439        no longer the case for positive assertions, except for (*ACCEPT). Again,
440        this sometimes improves Perl compatibility, and sometimes does not.
442    32. A number of tests that were in test 2 because Perl did things differently
443        have been moved to test 1, because either Perl or PCRE has changed, and
444        these tests are now compatible.
446    32. Backtracking control verbs are now handled in the same way in JIT and
447        interpreter.
449    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
450        contained a forward subroutine reference caused a compile error.
452    34. Auto-detect and optimize limited repetitions in JIT.
454    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
455        blocking (*UTF) etc.
457    36. In the interpreter, maximizing pattern repetitions for characters and
458        character types now use tail recursion, which reduces stack usage.
460    37. The value of the max lookbehind was not correctly preserved if a compiled
461        and saved regex was reloaded on a host of different endianness.
463    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
464        of the compiled pattern block, expand the flags field from 16 to 32 bits
465        because it was almost full.
467    39. Try madvise first before posix_madvise.
469    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
470        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
471        original change locked out all matches of empty strings. This has been
472        changed so that one match of an empty string per line is recognized.
473        Subsequent searches on the same line (for colouring or for --only-matching,
474        for example) do not recognize empty strings.
476    41. Applied a user patch to fix a number of spelling mistakes in comments.
478    42. Data lines longer than 65536 caused pcretest to crash.
480    43. Clarified the data type for length and startoffset arguments for pcre_exec
481        and pcre_dfa_exec in the function-specific man pages, where they were
482        explicitly stated to be in bytes, never having been updated. I also added
483        some clarification to the pcreapi man page.
485    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
486        a segmentation fault.
489    Version 8.32 30-November-2012
490    -----------------------------
492    1.  Improved JIT compiler optimizations for first character search and single
493        character iterators.
495    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
496        Patch by Daniel Richard G.
498    3.  Single character iterator optimizations in the JIT compiler.
500    4.  Improved JIT compiler optimizations for character ranges.
502    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
503        Reported by Giuseppe D'Angelo.
505    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
506        of a line, was being set incorrectly in cases where .* appeared inside
507        atomic brackets at the start of a pattern, or where there was a subsequent
508        *PRUNE or *SKIP.
510    7.  Improved instruction cache flush for POWER/PowerPC.
511        Patch by Daniel Richard G.
513    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
514        grep:
516        (a) There is now no limit to the number of patterns to be matched.
518        (b) An error is given if a pattern is too long.
520        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
521            are now supported.
523        (d) --exclude-from and --include-from (multiple use) have been added.
525        (e) Exclusions and inclusions now apply to all files and directories, not
526            just to those obtained from scanning a directory recursively.
528        (f) Multiple uses of -f and --file-list are now supported.
530        (g) In a Windows environment, the default for -d has been changed from
531            "read" (the GNU grep default) to "skip", because otherwise the presence
532            of a directory in the file list provokes an error.
534        (h) The documentation has been revised and clarified in places.
536    9.  Improve the matching speed of capturing brackets.
538    10. Changed the meaning of \X so that it now matches a Unicode extended
539        grapheme cluster.
541    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
542        out POSIX threads when JIT support is configured.
544    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
546    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
547        structure could go wrong in environments where size_t is not the same size
548        as int.
550    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
551        set.
553    15. The EBCDIC support had decayed; later updates to the code had included
554        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
555        general tidy up of EBCDIC-related issues, and the documentation was also
556        not quite right. There is now a test that can be run on ASCII systems to
557        check some of the EBCDIC-related things (but is it not a full test).
559    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
560        in a small tidy to the code.
562    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
564    18. If the --only-matching (-o) option in pcregrep is specified multiple
565        times, each one causes appropriate output. For example, -o1 -o2 outputs the
566        substrings matched by the 1st and 2nd capturing parentheses. A separating
567        string can be specified by --om-separator (default empty).
569    19. Improving the first n character searches.
571    20. Turn case lists for horizontal and vertical white space into macros so that
572        they are defined only once.
574    21. This set of changes together give more compatible Unicode case-folding
575        behaviour for characters that have more than one other case when UCP
576        support is available.
578        (a) The Unicode property table now has offsets into a new table of sets of
579            three or more characters that are case-equivalent. The MultiStage2.py
580            script that generates these tables (the pcre_ucd.c file) now scans
581            CaseFolding.txt instead of UnicodeData.txt for character case
582            information.
584        (b) The code for adding characters or ranges of characters to a character
585            class has been abstracted into a generalized function that also handles
586            case-independence. In UTF-mode with UCP support, this uses the new data
587            to handle characters with more than one other case.
589        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
590            whose other case is greater than 256 are now correctly matched
591            caselessly. Previously, the high codepoint matched the low one, but not
592            vice versa.
594        (d) The processing of \h, \H, \v, and \ in character classes now makes use
595            of the new class addition function, using character lists defined as
596            macros alongside the case definitions of 20 above.
598        (e) Caseless back references now work with characters that have more than
599            one other case.
601        (f) General caseless matching of characters with more than one other case
602            is supported.
604    22. Unicode character properties were updated from Unicode 6.2.0
606    23. Improved CMake support under Windows. Patch by Daniel Richard G.
608    24. Add support for 32-bit character strings, and UTF-32
610    25. Major JIT compiler update (code refactoring and bugfixing).
611        Experimental Sparc 32 support is added.
613    26. Applied a modified version of Daniel Richard G's patch to create
614        pcre.h.generic and config.h.generic by "make" instead of in the
615        PrepareRelease script.
617    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
618        pcre_compile.c when checking for a zero character.
620    28. Introducing a native interface for JIT. Through this interface, the compiled
621        machine code can be directly executed. The purpose of this interface is to
622        provide fast pattern matching, so several sanity checks are not performed.
623        However, feature tests are still performed. The new interface provides
624        1.4x speedup compared to the old one.
626    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
627        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
628        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
630    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
631        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
632        the "old" RFC 2279). Instead, it ended up passing a negative length to
633        pcre_exec().
635    31. Add support for GCC's visibility feature to hide internal functions.
637    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
638        "unknown -C option" after outputting 0 or 1.
640    33. There is now support for generating a code coverage report for the test
641        suite in environments where gcc is the compiler and lcov is installed. This
642        is mainly for the benefit of the developers.
644    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
645        unaddressable using valgrind annotations, allowing valgrind to detect
646        invalid memory accesses. This is mainly for the benefit of the developers.
648    25. (*UTF) can now be used to start a pattern in any of the three libraries.
650    26. Give configure error if --enable-cpp but no C++ compiler found.
653    Version 8.31 06-July-2012
654    -------------------------
656  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
658  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
660  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
661      to unsigned type, result still unsigned" that was given by an MS compiler      to unsigned type, result still unsigned" that was given by an MS compiler
662      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
664  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
# Line 18  Version 8.31 Line 667  Version 8.31
667      of more than one character:      of more than one character:
669      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
670          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
671          references.          references.
673      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
674          subject.          subject.
676      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
677          characters at the end of the subject.          characters at the end of the subject.
679      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
# Line 33  Version 8.31 Line 682  Version 8.31
682      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
683          a partial match for a CR character at the end of the subject string.          a partial match for a CR character at the end of the subject string.
685  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
686      running pcretest, the text "(JIT)" added to the output whenever JIT is      running pcretest, the text "(JIT)" added to the output whenever JIT is
687      actually used to run the match.      actually used to run the match.
689  7.  Individual JIT compile options can be set in pcretest by following -s+[+]  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
690      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
692  8.  OP_NOT now supports any UTF character not just single-byte ones.  8.  OP_NOT now supports any UTF character not just single-byte ones.
# Line 46  Version 8.31 Line 695  Version 8.31
696  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
697      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
701  12. Applied a (slightly modified) user-supplied patch that improves performance  12. Applied a (slightly modified) user-supplied patch that improves performance
702      when the heap is used for recursion (compiled with --disable-stack-for-      when the heap is used for recursion (compiled with --disable-stack-for-
703      recursion). Instead of malloc and free for each heap frame each time a      recursion). Instead of malloc and free for each heap frame each time a
704      logical recursion happens, frames are retained on a chain and re-used where      logical recursion happens, frames are retained on a chain and re-used where
705      possible. This sometimes gives as much as 30% improvement.      possible. This sometimes gives as much as 30% improvement.
707  13. (*COMMIT) is now correctly confined to within a recursive subpattern call.  13. As documented, (*COMMIT) is now confined to within a recursive subpattern
708        call.
710    14. As documented, (*COMMIT) is now confined to within a positive assertion.
712    15. It is now possible to link pcretest with libedit as an alternative to
713        libreadline.
715    16. (*COMMIT) control verb is now supported by the JIT compiler.
717    17. The Unicode data tables have been updated to Unicode 6.1.0.
719    18. Added --file-list option to pcregrep.
721    19. Added binary file support to pcregrep, including the -a, --binary-files,
722        -I, and --text options.
724    20. The madvise function is renamed for posix_madvise for QNX compatibility
725        reasons. Fixed by Giuseppe D'Angelo.
727    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
729    22. Changed the option for creating symbolic links for 16-bit man pages from
730        -s to -sf so that re-installing does not cause issues.
732    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
734    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
735        matches in certain environments (the workspace was not being correctly
736        retained). Also added to pcre_dfa_exec() a simple plausibility check on
737        some of the workspace data at the beginning of a restart.
739    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
740        was not doing so when it should - probably a typo introduced by SVN 528
741        (change 8.10/14).
743    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
744        \w+ when the character tables indicated that \x{c4} was a word character.
745        There were several related cases, all because the tests for doing a table
746        lookup were testing for characters less than 127 instead of 255.
748    27. If a pattern contains capturing parentheses that are not used in a match,
749        their slots in the ovector are set to -1. For those that are higher than
750        any matched groups, this happens at the end of processing. In the case when
751        there were back references that the ovector was too small to contain
752        (causing temporary malloc'd memory to be used during matching), and the
753        highest capturing number was not used, memory off the end of the ovector
754        was incorrectly being set to -1. (It was using the size of the temporary
755        memory instead of the true size.)
757    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
758        ovector size, it uses memory at the end of the block that it has got.
760    29. Check for an overlong MARK name and give an error at compile time. The
761        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
763    30. JIT compiler update.
765    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
766        Rill for the patch.
768    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
770    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
772    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
773        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
774        was enabled.
776    35. Improve JIT code generation for greedy plus quantifier.
778    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
779        1 to "aa" instead of to an empty string. The bug affected repeated groups
780        that could potentially match an empty string.
782    37. Optimizing single character iterators in JIT.
784    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
785        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
786        codepoints that are too big for the mode are faulted, and in a UTF mode,
787        disallowed codepoints are also faulted.
789    39. If PCRE was compiled with UTF support, in three places in the DFA
790        matcher there was code that should only have been obeyed in UTF mode, but
791        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
792        processing when bytes with values greater than 127 were present. In 16-bit
793        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
794        both cases the values are those that cannot be the first data item in a UTF
795        character. The three items that might have provoked this were recursions,
796        possessively repeated groups, and atomic groups.
798    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
799        and pcregrep, because some OS require shared objects to be explicitly
800        passed to ld, causing the link step to fail if they are not.
802    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
803        mode, patterns that started with \h* or \R* might be incorrectly matched.
806  Version 8.30 04-February-2012  Version 8.30 04-February-2012
# Line 1248  Version 7.9 11-Apr-09 Line 1993  Version 7.9 11-Apr-09
1993  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
1994      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
1995      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1996      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1997        8.33.]
1999  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
2000      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1491  Version 7.7 07-May-08 Line 2237  Version 7.7 07-May-08
2237      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2238      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2239      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2240      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2241      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2242      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.934  
changed lines
  Added in v.1462

  ViewVC Help
Powered by ViewVC 1.1.5