ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 1405 by ph10, Mon Nov 25 15:09:21 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  Version 8.34 19-November-2013
5    -----------------------------
7    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8        executable memory. Patch inspired by Carsten Klein.
10    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
11        this macro is never tested and has no effect, because the work to support
12        coverage involves only compiling and linking options and special targets in
13        the Makefile. The comment in config.h implied that defining the macro would
14        enable coverage support, which is totally false. There was also support for
15        setting this macro in the CMake files (my fault, I just copied it from
16        configure). SUPPORT_GCOV has now been removed.
18    3.  Make a small performance improvement in strlen16() and strlen32() in
19        pcretest.
21    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
22        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
23        these cases). There was also one in pcretest.c.
25    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
27    6.  In UTF mode, the code for checking whether a group could match an empty
28        string (which is used for indefinitely repeated groups to allow for
29        breaking an infinite loop) was broken when the group contained a repeated
30        negated single-character class with a character that occupied more than one
31        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
32        UTF-8 mode). The effect was undefined: the group might or might not be
33        deemed as matching an empty string, or the program might have crashed.
35    7.  The code for checking whether a group could match an empty string was not
36        recognizing that \h, \H, \v, \V, and \R must match a character.
38    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
39        an empty string. If it can, pcretest shows this in its information output.
41    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
42        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
43        matched by pcre_exec() without using JIT:
45        (a) If the rest of the pattern did not match after a maximal run of
46            grapheme clusters, the code for backing up to try with fewer of them
47            did not always back up over a full grapheme when characters that do not
48            have the modifier quality were involved, e.g. Hangul syllables.
50        (b) If the match point in a subject started with modifier character, and
51            there was no match, the code could incorrectly back up beyond the match
52            point, and potentially beyond the first character in the subject,
53            leading to a segfault or an incorrect match result.
55    10. A conditional group with an assertion condition could lead to PCRE
56        recording an incorrect first data item for a match if no other first data
57        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
58        first data item, and therefore matched "ca" after "c" instead of at the
59        start.
61    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
62        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
64    12. The source of pcregrep now includes z/OS-specific code so that it can be
65        compiled for z/OS as part of the special z/OS distribution.
67    13. Added the -T and -TM options to pcretest.
69    14. The code in pcre_compile.c for creating the table of named capturing groups
70        has been refactored. Instead of creating the table dynamically during the
71        actual compiling pass, the information is remembered during the pre-compile
72        pass (on the stack unless there are more than 20 named groups, in which
73        case malloc() is used) and the whole table is created before the actual
74        compile happens. This has simplified the code (it is now nearly 150 lines
75        shorter) and prepared the way for better handling of references to groups
76        with duplicate names.
78    15. A back reference to a named subpattern when there is more than one of the
79        same name now checks them in the order in which they appear in the pattern.
80        The first one that is set is used for the reference. Previously only the
81        first one was inspected. This change makes PCRE more compatible with Perl.
83    16. Unicode character properties were updated from Unicode 6.3.0.
85    17. The compile-time code for auto-possessification has been refactored, based
86        on a patch by Zoltan Herczeg. It now happens after instead of during
87        compilation. The code is cleaner, and more cases are handled. The option
88        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
89        options in pcretest are provided to set it. It can also be set by
90        (*NO_AUTO_POSSESS) at the start of a pattern.
92    18. The character VT has been added to the default ("C" locale) set of
93        characters that match \s and are generally treated as white space,
94        following this same change in Perl 5.18. There is now no difference between
95        "Perl space" and "POSIX space". Whether VT is treated as white space in
96        other locales depends on the locale.
98    19. The code for checking named groups as conditions, either for being set or
99        for being recursed, has been refactored (this is related to 14 and 15
100        above). Processing unduplicated named groups should now be as fast at
101        numerical groups, and processing duplicated groups should be faster than
102        before.
104    20. Two patches to the CMake build system, by Alexander Barkov:
106          (1) Replace the "source" command by "." in CMakeLists.txt because
107              "source" is a bash-ism.
109          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
110              without these the CMake build does not work on Solaris.
112    21. Perl has changed its handling of \8 and \9. If there is no previously
113        encountered capturing group of those numbers, they are treated as the
114        literal characters 8 and 9 instead of a binary zero followed by the
115        literals. PCRE now does the same.
117    22. Following Perl, added \o{} to specify codepoints in octal, making it
118        possible to specify values greater than 0777 and also making them
119        unambiguous.
121    23. Perl now gives an error for missing closing braces after \x{... instead of
122        treating the string as literal. PCRE now does the same.
124    24. RunTest used to grumble if an inappropriate test was selected explicitly,
125        but just skip it when running all tests. This make it awkward to run ranges
126        of tests when one of them was inappropriate. Now it just skips any
127        inappropriate tests, as it always did when running all tests.
129    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
130        character types such as \d or \w, too many callouts were inserted, and the
131        data that they returned was rubbish.
133    26. In UCP mode, \s was not matching two of the characters that Perl matches,
134        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
135        were matched by \h. The code has now been refactored so that the lists of
136        the horizontal and vertical whitespace characters used for \h and \v (which
137        are defined only in one place) are now also used for \s.
139    27. Add JIT support for the 64 bit TileGX architecture.
140        Patch by Jiong Wang (Tilera Corporation).
142    28. Possessive quantifiers for classes (both explicit and automatically
143        generated) now use special opcodes instead of wrapping in ONCE brackets.
145    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
146        (because it's meaningless), this was not happening when PCRE_CASELESS was
147        set. Not wrong, but inefficient.
149    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
150        properties for \w, \d, etc) is present in a test regex. Otherwise if the
151        test contains no characters greater than 255, Perl doesn't realise it
152        should be using Unicode semantics.
154    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
155        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
156        does in Unicode mode.
158    32. Added the "forbid" facility to pcretest so that putting tests into the
159        wrong test files can sometimes be quickly detected.
161    33. There is now a limit (default 250) on the depth of nesting of parentheses.
162        This limit is imposed to control the amount of system stack used at compile
163        time. It can be changed at build time by --with-parens-nest-limit=xxx or
164        the equivalent in CMake.
166    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
167        errors. Perl warns for these when in warning mode, but PCRE has no facility
168        for giving warnings.
170    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
171        However, this was not working for (?!) because it is optimized to (*FAIL),
172        for which PCRE does not allow quantifiers. The optimization is now disabled
173        when a quantifier follows (?!). I can't see any use for this, but it makes
174        things uniform.
176    36. Perl no longer allows group names to start with digits, so I have made this
177        change also in PCRE. It simplifies the code a bit.
179    37. In extended mode, Perl ignores spaces before a + that indicates a
180        possessive quantifier. PCRE allowed a space before the quantifier, but not
181        before the possessive +. It now does.
183    38. The use of \K (reset reported match start) within a repeated possessive
184        group such as (a\Kb)*+ was not working.
186    40. Document that the same character tables must be used at compile time and
187        run time, and that the facility to pass tables to pcre_exec() and
188        pcre_dfa_exec() is for use only with saved/restored patterns.
191    Version 8.33 28-May-2013
192    ------------------------
194    1.  Added 'U' to some constants that are compared to unsigned integers, to
195        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
196        variables that are added to signed variables, to ensure the result is
197        signed and can be negated.
199    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
200        CMake config files.
202    3.  Revise the creation of config.h.generic so that all boolean macros are
203        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
204        overriding via -D on the command line possible.
206    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
207        to unsigned int is reported to make a quite noticeable speed difference in
208        a specific Windows environment. Testing on Linux did also appear to show
209        some benefit (and it is clearly not harmful). Also fixed the definition of
210        Xop which should be unsigned.
212    5.  Related to (4), changing the definition of the intermediate variable cc
213        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
214        improvements.
216    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
217        unnecessary spaces.
219    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
220        and later.
222    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
224    9.  Optimizing fast_forward_start_bits in JIT.
226    10. Adding support for callouts in JIT, and fixing some issues revealed
227        during this work. Namely:
229        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
231        (b) Minimum length was not checked before the matching is started.
233    11. The value of capture_last that is passed to callouts was incorrect in some
234        cases when there was a capture on one path that was subsequently abandoned
235        after a backtrack. Also, the capture_last value is now reset after a
236        recursion, since all captures are also reset in this case.
238    12. The interpreter no longer returns the "too many substrings" error in the
239        case when an overflowing capture is in a branch that is subsequently
240        abandoned after a backtrack.
242    13. In the pathological case when an offset vector of size 2 is used, pcretest
243        now prints out the matched string after a yield of 0 or 1.
245    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
246        Only supported by the JIT compiler at the moment.
248    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
250    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
251        offset of the starting point of the matching process, provided the offsets
252        vector is large enough.
254    17. The \A escape now records a lookbehind value of 1, though its execution
255        does not actually inspect the previous character. This is to ensure that,
256        in partial multi-segment matching, at least one character from the old
257        segment is retained when a new segment is processed. Otherwise, if there
258        are no lookbehinds in the pattern, \A might match incorrectly at the start
259        of a new segment.
261    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
263    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
264        gives some modest performance improvement in 8-bit mode.
266    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
267        be expressed in certain programming languages using Universal Character
268        Names.
270    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
271        which points out that "non characters" are not "characters that may not
272        appear in Unicode strings" but rather "characters that are reserved for
273        internal use and have only local meaning".
275    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
276        there was a conditional group that depended on an assertion, if the
277        assertion was false, the callout that immediately followed the alternation
278        in the condition was skipped when pcre_exec() was used for matching.
280    23. Allow an explicit callout to be inserted before an assertion that is the
281        condition for a conditional group, for compatibility with automatic
282        callouts, which always insert a callout at this point.
284    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
285        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
287    25. (*PRUNE) is now supported by the JIT compiler.
289    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
291    27. Fix the case where there are two or more SKIPs with arguments that may be
292        ignored.
294    28. (*SKIP) is now supported by the JIT compiler.
296    29. (*THEN) is now supported by the JIT compiler.
298    30. Update RunTest with additional test selector options.
300    31. The way PCRE handles backtracking verbs has been changed in two ways.
302        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
303        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
304        backtracking. In some cases this makes it more Perl-compatible, but Perl's
305        rather obscure rules do not always do the same thing.
307        (2) Previously, backtracking verbs were confined within assertions. This is
308        no longer the case for positive assertions, except for (*ACCEPT). Again,
309        this sometimes improves Perl compatibility, and sometimes does not.
311    32. A number of tests that were in test 2 because Perl did things differently
312        have been moved to test 1, because either Perl or PCRE has changed, and
313        these tests are now compatible.
315    32. Backtracking control verbs are now handled in the same way in JIT and
316        interpreter.
318    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
319        contained a forward subroutine reference caused a compile error.
321    34. Auto-detect and optimize limited repetitions in JIT.
323    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
324        blocking (*UTF) etc.
326    36. In the interpreter, maximizing pattern repetitions for characters and
327        character types now use tail recursion, which reduces stack usage.
329    37. The value of the max lookbehind was not correctly preserved if a compiled
330        and saved regex was reloaded on a host of different endianness.
332    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
333        of the compiled pattern block, expand the flags field from 16 to 32 bits
334        because it was almost full.
336    39. Try madvise first before posix_madvise.
338    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
339        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
340        original change locked out all matches of empty strings. This has been
341        changed so that one match of an empty string per line is recognized.
342        Subsequent searches on the same line (for colouring or for --only-matching,
343        for example) do not recognize empty strings.
345    41. Applied a user patch to fix a number of spelling mistakes in comments.
347    42. Data lines longer than 65536 caused pcretest to crash.
349    43. Clarified the data type for length and startoffset arguments for pcre_exec
350        and pcre_dfa_exec in the function-specific man pages, where they were
351        explicitly stated to be in bytes, never having been updated. I also added
352        some clarification to the pcreapi man page.
354    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
355        a segmentation fault.
358    Version 8.32 30-November-2012
359    -----------------------------
361    1.  Improved JIT compiler optimizations for first character search and single
362        character iterators.
364    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
365        Patch by Daniel Richard G.
367    3.  Single character iterator optimizations in the JIT compiler.
369    4.  Improved JIT compiler optimizations for character ranges.
371    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
372        Reported by Giuseppe D'Angelo.
374    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
375        of a line, was being set incorrectly in cases where .* appeared inside
376        atomic brackets at the start of a pattern, or where there was a subsequent
377        *PRUNE or *SKIP.
379    7.  Improved instruction cache flush for POWER/PowerPC.
380        Patch by Daniel Richard G.
382    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
383        grep:
385        (a) There is now no limit to the number of patterns to be matched.
387        (b) An error is given if a pattern is too long.
389        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
390            are now supported.
392        (d) --exclude-from and --include-from (multiple use) have been added.
394        (e) Exclusions and inclusions now apply to all files and directories, not
395            just to those obtained from scanning a directory recursively.
397        (f) Multiple uses of -f and --file-list are now supported.
399        (g) In a Windows environment, the default for -d has been changed from
400            "read" (the GNU grep default) to "skip", because otherwise the presence
401            of a directory in the file list provokes an error.
403        (h) The documentation has been revised and clarified in places.
405    9.  Improve the matching speed of capturing brackets.
407    10. Changed the meaning of \X so that it now matches a Unicode extended
408        grapheme cluster.
410    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
411        out POSIX threads when JIT support is configured.
413    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
415    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
416        structure could go wrong in environments where size_t is not the same size
417        as int.
419    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
420        set.
422    15. The EBCDIC support had decayed; later updates to the code had included
423        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
424        general tidy up of EBCDIC-related issues, and the documentation was also
425        not quite right. There is now a test that can be run on ASCII systems to
426        check some of the EBCDIC-related things (but is it not a full test).
428    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
429        in a small tidy to the code.
431    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
433    18. If the --only-matching (-o) option in pcregrep is specified multiple
434        times, each one causes appropriate output. For example, -o1 -o2 outputs the
435        substrings matched by the 1st and 2nd capturing parentheses. A separating
436        string can be specified by --om-separator (default empty).
438    19. Improving the first n character searches.
440    20. Turn case lists for horizontal and vertical white space into macros so that
441        they are defined only once.
443    21. This set of changes together give more compatible Unicode case-folding
444        behaviour for characters that have more than one other case when UCP
445        support is available.
447        (a) The Unicode property table now has offsets into a new table of sets of
448            three or more characters that are case-equivalent. The MultiStage2.py
449            script that generates these tables (the pcre_ucd.c file) now scans
450            CaseFolding.txt instead of UnicodeData.txt for character case
451            information.
453        (b) The code for adding characters or ranges of characters to a character
454            class has been abstracted into a generalized function that also handles
455            case-independence. In UTF-mode with UCP support, this uses the new data
456            to handle characters with more than one other case.
458        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
459            whose other case is greater than 256 are now correctly matched
460            caselessly. Previously, the high codepoint matched the low one, but not
461            vice versa.
463        (d) The processing of \h, \H, \v, and \ in character classes now makes use
464            of the new class addition function, using character lists defined as
465            macros alongside the case definitions of 20 above.
467        (e) Caseless back references now work with characters that have more than
468            one other case.
470        (f) General caseless matching of characters with more than one other case
471            is supported.
473    22. Unicode character properties were updated from Unicode 6.2.0
475    23. Improved CMake support under Windows. Patch by Daniel Richard G.
477    24. Add support for 32-bit character strings, and UTF-32
479    25. Major JIT compiler update (code refactoring and bugfixing).
480        Experimental Sparc 32 support is added.
482    26. Applied a modified version of Daniel Richard G's patch to create
483        pcre.h.generic and config.h.generic by "make" instead of in the
484        PrepareRelease script.
486    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
487        pcre_compile.c when checking for a zero character.
489    28. Introducing a native interface for JIT. Through this interface, the compiled
490        machine code can be directly executed. The purpose of this interface is to
491        provide fast pattern matching, so several sanity checks are not performed.
492        However, feature tests are still performed. The new interface provides
493        1.4x speedup compared to the old one.
495    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
496        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
497        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
499    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
500        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
501        the "old" RFC 2279). Instead, it ended up passing a negative length to
502        pcre_exec().
504    31. Add support for GCC's visibility feature to hide internal functions.
506    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
507        "unknown -C option" after outputting 0 or 1.
509    33. There is now support for generating a code coverage report for the test
510        suite in environments where gcc is the compiler and lcov is installed. This
511        is mainly for the benefit of the developers.
513    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
514        unaddressable using valgrind annotations, allowing valgrind to detect
515        invalid memory accesses. This is mainly for the benefit of the developers.
517    25. (*UTF) can now be used to start a pattern in any of the three libraries.
519    26. Give configure error if --enable-cpp but no C++ compiler found.
522    Version 8.31 06-July-2012
523    -------------------------
525    1.  Fixing a wrong JIT test case and some compiler warnings.
527    2.  Removed a bashism from the RunTest script.
529    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
530        to unsigned type, result still unsigned" that was given by an MS compiler
531        on encountering the code "-sizeof(xxx)".
533    4.  Partial matching support is added to the JIT compiler.
535    5.  Fixed several bugs concerned with partial matching of items that consist
536        of more than one character:
538        (a) /^(..)\1/ did not partially match "aba" because checking references was
539            done on an "all or nothing" basis. This also applied to repeated
540            references.
542        (b) \R did not give a hard partial match if \r was found at the end of the
543            subject.
545        (c) \X did not give a hard partial match after matching one or more
546            characters at the end of the subject.
548        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
549            a partial match for the string "\r".
551        (e) When newline was set to CRLF, the metacharacter "." did not recognize
552            a partial match for a CR character at the end of the subject string.
554    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
555        running pcretest, the text "(JIT)" added to the output whenever JIT is
556        actually used to run the match.
558    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
559        or /S+[+] with a digit between 1 and 7.
561    8.  OP_NOT now supports any UTF character not just single-byte ones.
563    9.  (*MARK) control verb is now supported by the JIT compiler.
565    10. The command "./RunTest list" lists the available tests without actually
566        running any of them. (Because I keep forgetting what they all are.)
570    12. Applied a (slightly modified) user-supplied patch that improves performance
571        when the heap is used for recursion (compiled with --disable-stack-for-
572        recursion). Instead of malloc and free for each heap frame each time a
573        logical recursion happens, frames are retained on a chain and re-used where
574        possible. This sometimes gives as much as 30% improvement.
576    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
577        call.
579    14. As documented, (*COMMIT) is now confined to within a positive assertion.
581    15. It is now possible to link pcretest with libedit as an alternative to
582        libreadline.
584    16. (*COMMIT) control verb is now supported by the JIT compiler.
586    17. The Unicode data tables have been updated to Unicode 6.1.0.
588    18. Added --file-list option to pcregrep.
590    19. Added binary file support to pcregrep, including the -a, --binary-files,
591        -I, and --text options.
593    20. The madvise function is renamed for posix_madvise for QNX compatibility
594        reasons. Fixed by Giuseppe D'Angelo.
596    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
598    22. Changed the option for creating symbolic links for 16-bit man pages from
599        -s to -sf so that re-installing does not cause issues.
601    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
603    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
604        matches in certain environments (the workspace was not being correctly
605        retained). Also added to pcre_dfa_exec() a simple plausibility check on
606        some of the workspace data at the beginning of a restart.
608    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
609        was not doing so when it should - probably a typo introduced by SVN 528
610        (change 8.10/14).
612    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
613        \w+ when the character tables indicated that \x{c4} was a word character.
614        There were several related cases, all because the tests for doing a table
615        lookup were testing for characters less than 127 instead of 255.
617    27. If a pattern contains capturing parentheses that are not used in a match,
618        their slots in the ovector are set to -1. For those that are higher than
619        any matched groups, this happens at the end of processing. In the case when
620        there were back references that the ovector was too small to contain
621        (causing temporary malloc'd memory to be used during matching), and the
622        highest capturing number was not used, memory off the end of the ovector
623        was incorrectly being set to -1. (It was using the size of the temporary
624        memory instead of the true size.)
626    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
627        ovector size, it uses memory at the end of the block that it has got.
629    29. Check for an overlong MARK name and give an error at compile time. The
630        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
632    30. JIT compiler update.
634    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
635        Rill for the patch.
637    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
639    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
641    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
642        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
643        was enabled.
645    35. Improve JIT code generation for greedy plus quantifier.
647    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
648        1 to "aa" instead of to an empty string. The bug affected repeated groups
649        that could potentially match an empty string.
651    37. Optimizing single character iterators in JIT.
653    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
654        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
655        codepoints that are too big for the mode are faulted, and in a UTF mode,
656        disallowed codepoints are also faulted.
658    39. If PCRE was compiled with UTF support, in three places in the DFA
659        matcher there was code that should only have been obeyed in UTF mode, but
660        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
661        processing when bytes with values greater than 127 were present. In 16-bit
662        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
663        both cases the values are those that cannot be the first data item in a UTF
664        character. The three items that might have provoked this were recursions,
665        possessively repeated groups, and atomic groups.
667    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
668        and pcregrep, because some OS require shared objects to be explicitly
669        passed to ld, causing the link step to fail if they are not.
671    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
672        mode, patterns that started with \h* or \R* might be incorrectly matched.
675    Version 8.30 04-February-2012
676    -----------------------------
678    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
679        name is defined in ctype.h.
681    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
682        only in quite long subpatterns.
684    3.  Removed the function pcre_info(), which has been obsolete and deprecated
685        since it was replaced by pcre_fullinfo() in February 2000.
687    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
688        match a (*MARK), and the match failed at the start of the subject, a
689        reference to memory before the start of the subject could occur. This bug
690        was introduced by fix 17 of release 8.21.
692    5.  A reference to an unset group with zero minimum repetition was giving
693        totally wrong answers (in non-JavaScript-compatibility mode). For example,
694        /(another)?(\1?)test/ matched against "hello world test". This bug was
695        introduced in release 8.13.
697    6.  Add support for 16-bit character strings (a large amount of work involving
698        many changes and refactorings).
700    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
701        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
702        from a file.
704    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
705        rounding is not applied in this particular case).
707    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
708        if they appear, or are escaped, in patterns.
710    10. Get rid of a number of -Wunused-but-set-variable warnings.
712    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
713        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
714        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
715        also returns the mark "x". This bug applied to capturing parentheses,
716        non-capturing parentheses, and atomic parentheses. It also applied to some
717        assertions.
719    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
720        information out of configure.ac instead of relying on pcre.h.generic, which
721        is not stored in the repository.
723    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
724        -lreadline.
726    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
728    15. Applied Graycode's patch to put the top-level frame on the stack rather
729        than the heap when not using the stack for recursion. This gives a
730        performance improvement in many cases when recursion is not deep.
732    16. Experimental code added to "pcretest -C" to output the stack frame size.
735    Version 8.21 12-Dec-2011
736    ------------------------
738    1.  Updating the JIT compiler.
740    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
741        are added as well.
743    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
744        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
745        calling _pcre_jit_exec. Some extra comments are added.
747    4.  (*MARK) settings inside atomic groups that do not contain any capturing
748        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
749        was introduced by change 18 for 8.20.
751    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
752        ECMA-262 standard.
754    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
755        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
756        This bug was probably introduced by change 9 of 8.13.
758    7.  While fixing 6 above, I noticed that a number of other items were being
759        incorrectly rejected as "not fixed length". This arose partly because newer
760        opcodes had not been added to the fixed-length checking code. I have (a)
761        corrected the bug and added tests for these items, and (b) arranged for an
762        error to occur if an unknown opcode is encountered while checking for fixed
763        length instead of just assuming "not fixed length". The items that were
764        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
765        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
766        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
768    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
769        being incorrectly compiled and would have given unpredicatble results.
771    9.  A possessively repeated subpattern with minimum repeat count greater than
772        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
773        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
774        the first (A) could occur when it should not.
776    10. Add a cast and remove a redundant test from the code.
778    11. JIT should use pcre_malloc/pcre_free for allocation.
780    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
781        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
782        is anything other than /usr, -L is still shown).
784    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
786    14. Perl does not support \N without a following name in a [] class; PCRE now
787        also gives an error.
789    15. If a forward reference was repeated with an upper limit of around 2000,
790        it caused the error "internal error: overran compiling workspace". The
791        maximum number of forward references (including repeats) was limited by the
792        internal workspace, and dependent on the LINK_SIZE. The code has been
793        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
794        the default depends on LINK_SIZE. There is a new upper limit (for safety)
795        of around 200,000 forward references. While doing this, I also speeded up
796        the filling in of repeated forward references.
798    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
799        incorrectly expecting the subject to contain another "a" after the start.
801    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
802        in the match, the SKIP should be ignored. This was not happening; instead
803        the SKIP was being treated as NOMATCH. For patterns such as
804        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
805        tested.
807    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
808        now much more compatible with Perl, in particular in cases where the result
809        is a non-match for a non-anchored pattern. For example, if
810        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
811        "m", where previously it did not return a name. A side effect of this
812        change is that for partial matches, the last encountered mark name is
813        returned, as for non matches. A number of tests that were previously not
814        Perl-compatible have been moved into the Perl-compatible test files. The
815        refactoring has had the pleasing side effect of removing one argument from
816        the match() function, thus reducing its stack requirements.
818    19. If the /S+ option was used in pcretest to study a pattern using JIT,
819        subsequent uses of /S (without +) incorrectly behaved like /S+.
821    21. Retrieve executable code size support for the JIT compiler and fixing
822        some warnings.
824    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
825        not work when the shorter character appeared right at the end of the
826        subject string.
828    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
829        systems.
831    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
832        output it when the /M option is used in pcretest.
834    25. The CheckMan script was not being included in the distribution. Also, added
835        an explicit "perl" to run Perl scripts from the PrepareRelease script
836        because this is reportedly needed in Windows.
838    26. If study data was being save in a file and studying had not found a set of
839        "starts with" bytes for the pattern, the data written to the file (though
840        never used) was taken from uninitialized memory and so caused valgrind to
841        complain.
843    27. Updated RunTest.bat as provided by Sheri Pierce.
845    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
847    29. Computation of memory usage for the table of capturing group names was
848        giving an unnecessarily large value.
851    Version 8.20 21-Oct-2011
852    ------------------------
854    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
855        a POSIX class. After further experiments with Perl, which convinced me that
856        Perl has bugs and confusions, a closing square bracket is no longer allowed
857        in a POSIX name. This bug also affected patterns with classes that started
858        with full stops.
860    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
861        captured substring, but while checking the failing first alternative,
862        substring 1 is temporarily captured. If the output vector supplied to
863        pcre_exec() was not big enough for this capture, the yield of the function
864        was still zero ("insufficient space for captured substrings"). This cannot
865        be totally fixed without adding another stack variable, which seems a lot
866        of expense for a edge case. However, I have improved the situation in cases
867        such as /(a)(b)x|abc/ matched against "abc", where the return code
868        indicates that fewer than the maximum number of slots in the ovector have
869        been set.
871    3.  Related to (2) above: when there are more back references in a pattern than
872        slots in the output vector, pcre_exec() uses temporary memory during
873        matching, and copies in the captures as far as possible afterwards. It was
874        using the entire output vector, but this conflicts with the specification
875        that only 2/3 is used for passing back captured substrings. Now it uses
876        only the first 2/3, for compatibility. This is, of course, another edge
877        case.
879    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
880        main code base, and can be used by building with --enable-jit. When this is
881        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
882        runtime --no-jit option is given.
884    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
885        ovector, the return from the function was zero, implying that there were
886        other matches that did not fit. The correct "exactly full" value is now
887        returned.
889    6.  If a subpattern that was called recursively or as a subroutine contained
890        (*PRUNE) or any other control that caused it to give a non-standard return,
891        invalid errors such as "Error -26 (nested recursion at the same subject
892        position)" or even infinite loops could occur.
894    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
895        computing the minimum length on reaching *ACCEPT, and so ended up with the
896        wrong value of 1 rather than 0. Further investigation indicates that
897        computing a minimum subject length in the presence of *ACCEPT is difficult
898        (think back references, subroutine calls), and so I have changed the code
899        so that no minimum is registered for a pattern that contains *ACCEPT.
901    8.  If (*THEN) was present in the first (true) branch of a conditional group,
902        it was not handled as intended. [But see 16 below.]
904    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
905        Sheri Pierce.
907    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
908        the first byte in a match must be "a".
910    11. Change 17 for 8.13 increased the recursion depth for patterns like
911        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
912        pattern contains any instances of (*THEN). If it does not, the old
913        optimizations are restored. It would be nice to do this on a per-group
914        basis, but at the moment that is not feasible.
916    12. In some environments, the output of pcretest -C is CRLF terminated. This
917        broke RunTest's code that checks for the link size. A single white space
918        character after the value is now allowed for.
920    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
921        For "fr", it uses the Windows-specific input and output files.
923    14. If (*THEN) appeared in a group that was called recursively or as a
924        subroutine, it did not work as intended. [But see next item.]
926    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
927        pattern fragments (but not containing any | characters). If A and B are
928        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
929        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
930        D. In other words, Perl considers parentheses that do not contain any |
931        characters to be part of a surrounding alternative, whereas PCRE was
932        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
933        differently. PCRE now behaves in the same way as Perl, except in the case
934        of subroutine/recursion calls such as (?1) which have in any case always
935        been different (but PCRE had them first :-).
937    16. Related to 15 above: Perl does not treat the | in a conditional group as
938        creating alternatives. Such a group is treated in the same way as an
939        ordinary group without any | characters when processing (*THEN). PCRE has
940        been changed to match Perl's behaviour.
942    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
943        RunGrepTest script failed.
945    18. Change 22 for version 13 caused atomic groups to use more stack. This is
946        inevitable for groups that contain captures, but it can lead to a lot of
947        stack use in large patterns. The old behaviour has been restored for atomic
948        groups that do not contain any capturing parentheses.
950    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
951        suppress the check for a minimum subject length at run time. (If it was
952        given to pcre_exec() or pcre_dfa_exec() it did work.)
954    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
955        fail to work when decoding hex characters in data strings in EBCDIC
956        environments.
958    21. It appears that in at least one Mac OS environment, the isxdigit() function
959        is implemented as a macro that evaluates to its argument more than once,
960        contravening the C 90 Standard (I haven't checked a later standard). There
961        was an instance in pcretest which caused it to go wrong when processing
962        \x{...} escapes in subject strings. The has been rewritten to avoid using
963        things like p++ in the argument of isxdigit().
966    Version 8.13 16-Aug-2011
967  ------------------------  ------------------------
969  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 98  Version 8.13 02-Aug-2011 Line 1060  Version 8.13 02-Aug-2011
1060      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
1061      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
1062      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
1063      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
1065  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
1066      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 1151  Version 8.13 02-Aug-2011
1151      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1152      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
1153      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1154      more like Perl.      more like Perl. (But see 8.20/1 above.)
1156  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1157      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 1186  Version 8.13 02-Aug-2011
1186      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
1187          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
1189      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1190          PCRE is built.          PCRE is built.
1192      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 1207  Version 8.13 02-Aug-2011
1207  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1208      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
1209      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
1211  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1212      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
1215  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
# Line 900  Version 7.9 11-Apr-09 Line 1862  Version 7.9 11-Apr-09
1862  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
1863      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
1864      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1865      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1866        8.33.]
1868  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
1869      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 1143  Version 7.7 07-May-08 Line 2106  Version 7.7 07-May-08
2106      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2107      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2108      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2109      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2110      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2111      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.657  
changed lines
  Added in v.1405

  ViewVC Help
Powered by ViewVC 1.1.5