ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 742 by zherczeg, Sun Nov 6 08:05:33 2011 UTC revision 1221 by ph10, Sun Nov 11 20:27:03 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.21  Version 8.32 11-November-2012
5  ------------  -----------------------------
7    1.  Improved JIT compiler optimizations for first character search and single
8        character iterators.
10    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
11        Patch by Daniel Richard G.
13    3.  Single character iterator optimizations in the JIT compiler.
15    4.  Improved JIT compiler optimizations for character ranges.
17    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
18        Reported by Giuseppe D'Angelo.
20    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
21        of a line, was being set incorrectly in cases where .* appeared inside
22        atomic brackets at the start of a pattern, or where there was a subsequent
23        *PRUNE or *SKIP.
25    7.  Improved instruction cache flush for POWER/PowerPC.
26        Patch by Daniel Richard G.
28    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
29        grep:
31        (a) There is now no limit to the number of patterns to be matched.
33        (b) An error is given if a pattern is too long.
35        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
36            are now supported.
38        (d) --exclude-from and --include-from (multiple use) have been added.
40        (e) Exclusions and inclusions now apply to all files and directories, not
41            just to those obtained from scanning a directory recursively.
43        (f) Multiple uses of -f and --file-list are now supported.
45        (g) In a Windows environment, the default for -d has been changed from
46            "read" (the GNU grep default) to "skip", because otherwise the presence
47            of a directory in the file list provokes an error.
49        (h) The documentation has been revised and clarified in places.
51    9.  Improve the matching speed of capturing brackets.
53    10. Changed the meaning of \X so that it now matches a Unicode extended
54        grapheme cluster.
56    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
57        out POSIX threads when JIT support is configured.
59    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
61    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
62        structure could go wrong in environments where size_t is not the same size
63        as int.
65    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
66        set.
68    15. The EBCDIC support had decayed; later updates to the code had included
69        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
70        general tidy up of EBCDIC-related issues, and the documentation was also
71        not quite right. There is now a test that can be run on ASCII systems to
72        check some of the EBCDIC-related things (but is it not a full test).
74    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
75        in a small tidy to the code.
77    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
79    18. If the --only-matching (-o) option in pcregrep is specified multiple
80        times, each one causes appropriate output. For example, -o1 -o2 outputs the
81        substrings matched by the 1st and 2nd capturing parentheses. A separating
82        string can be specified by --om-separator (default empty).
84    19. Improving the first n character searches.
86    20. Turn case lists for horizontal and vertical white space into macros so that
87        they are defined only once.
89    21. This set of changes together give more compatible Unicode case-folding
90        behaviour for characters that have more than one other case when UCP
91        support is available.
93        (a) The Unicode property table now has offsets into a new table of sets of
94            three or more characters that are case-equivalent. The MultiStage2.py
95            script that generates these tables (the pcre_ucd.c file) now scans
96            CaseFolding.txt instead of UnicodeData.txt for character case
97            information.
99        (b) The code for adding characters or ranges of characters to a character
100            class has been abstracted into a generalized function that also handles
101            case-independence. In UTF-mode with UCP support, this uses the new data
102            to handle characters with more than one other case.
104        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
105            whose other case is greater than 256 are now correctly matched
106            caselessly. Previously, the high codepoint matched the low one, but not
107            vice versa.
109        (d) The processing of \h, \H, \v, and \ in character classes now makes use
110            of the new class addition function, using character lists defined as
111            macros alongside the case definitions of 20 above.
113        (e) Caseless back references now work with characters that have more than
114            one other case.
116        (f) General caseless matching of characters with more than one other case
117            is supported.
119    22. Unicode character properties were updated from Unicode 6.2.0
121    23. Improved CMake support under Windows. Patch by Daniel Richard G.
123    24. Add support for 32-bit character strings, and UTF-32
125    25. Major JIT compiler update (code refactoring and bugfixing).
126        Experimental Sparc 32 support is added.
128    26. Applied a modified version of Daniel Richard G's patch to create
129        pcre.h.generic and config.h.generic by "make" instead of in the
130        PrepareRelease script.
132    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
133        pcre_compile.c when checking for a zero character.
135    28. Introducing a native interface for JIT. Through this interface, the compiled
136        machine code can be directly executed. The purpose of this interface is to
137        provide fast pattern matching, so several sanity checks are not performed.
138        However, feature tests are still performed. The new interface provides
139        1.4x speedup compared to the old one.
141    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
142        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
143        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
145    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
146        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
147        the "old" RFC 2279). Instead, it ended up passing a negative length to
148        pcre_exec().
150    31. Add support for GCC's visibility feature to hide internal functions.
152    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
153        "unknown -C option" after outputting 0 or 1.
155    33. There is now support for generating a code coverage report for the test
156        suite in environments where gcc is the compiler and lcov is installed. This
157        is mainly for the benefit of the developers.
159    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
160        unaddressable using valgrind annotations, allowing valgrind to detect
161        invalid memory accesses. This is mainly for the benefit of the developers.
163    25. (*UTF) can now be used to start a pattern in any of the three libraries.
166    Version 8.31 06-July-2012
167    -------------------------
169    1.  Fixing a wrong JIT test case and some compiler warnings.
171    2.  Removed a bashism from the RunTest script.
173    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
174        to unsigned type, result still unsigned" that was given by an MS compiler
175        on encountering the code "-sizeof(xxx)".
177    4.  Partial matching support is added to the JIT compiler.
179    5.  Fixed several bugs concerned with partial matching of items that consist
180        of more than one character:
182        (a) /^(..)\1/ did not partially match "aba" because checking references was
183            done on an "all or nothing" basis. This also applied to repeated
184            references.
186        (b) \R did not give a hard partial match if \r was found at the end of the
187            subject.
189        (c) \X did not give a hard partial match after matching one or more
190            characters at the end of the subject.
192        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
193            a partial match for the string "\r".
195        (e) When newline was set to CRLF, the metacharacter "." did not recognize
196            a partial match for a CR character at the end of the subject string.
198    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
199        running pcretest, the text "(JIT)" added to the output whenever JIT is
200        actually used to run the match.
202    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
203        or /S+[+] with a digit between 1 and 7.
205    8.  OP_NOT now supports any UTF character not just single-byte ones.
207    9.  (*MARK) control verb is now supported by the JIT compiler.
209    10. The command "./RunTest list" lists the available tests without actually
210        running any of them. (Because I keep forgetting what they all are.)
214    12. Applied a (slightly modified) user-supplied patch that improves performance
215        when the heap is used for recursion (compiled with --disable-stack-for-
216        recursion). Instead of malloc and free for each heap frame each time a
217        logical recursion happens, frames are retained on a chain and re-used where
218        possible. This sometimes gives as much as 30% improvement.
220    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
221        call.
223    14. As documented, (*COMMIT) is now confined to within a positive assertion.
225    15. It is now possible to link pcretest with libedit as an alternative to
226        libreadline.
228    16. (*COMMIT) control verb is now supported by the JIT compiler.
230    17. The Unicode data tables have been updated to Unicode 6.1.0.
232    18. Added --file-list option to pcregrep.
234    19. Added binary file support to pcregrep, including the -a, --binary-files,
235        -I, and --text options.
237    20. The madvise function is renamed for posix_madvise for QNX compatibility
238        reasons. Fixed by Giuseppe D'Angelo.
240    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
242    22. Changed the option for creating symbolic links for 16-bit man pages from
243        -s to -sf so that re-installing does not cause issues.
245    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
247    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
248        matches in certain environments (the workspace was not being correctly
249        retained). Also added to pcre_dfa_exec() a simple plausibility check on
250        some of the workspace data at the beginning of a restart.
252    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
253        was not doing so when it should - probably a typo introduced by SVN 528
254        (change 8.10/14).
256    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
257        \w+ when the character tables indicated that \x{c4} was a word character.
258        There were several related cases, all because the tests for doing a table
259        lookup were testing for characters less than 127 instead of 255.
261    27. If a pattern contains capturing parentheses that are not used in a match,
262        their slots in the ovector are set to -1. For those that are higher than
263        any matched groups, this happens at the end of processing. In the case when
264        there were back references that the ovector was too small to contain
265        (causing temporary malloc'd memory to be used during matching), and the
266        highest capturing number was not used, memory off the end of the ovector
267        was incorrectly being set to -1. (It was using the size of the temporary
268        memory instead of the true size.)
270    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
271        ovector size, it uses memory at the end of the block that it has got.
273    29. Check for an overlong MARK name and give an error at compile time. The
274        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
276    30. JIT compiler update.
278    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
279        Rill for the patch.
281    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
283    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
285    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
286        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
287        was enabled.
289    35. Improve JIT code generation for greedy plus quantifier.
291    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
292        1 to "aa" instead of to an empty string. The bug affected repeated groups
293        that could potentially match an empty string.
295    37. Optimizing single character iterators in JIT.
297    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
298        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
299        codepoints that are too big for the mode are faulted, and in a UTF mode,
300        disallowed codepoints are also faulted.
302    39. If PCRE was compiled with UTF support, in three places in the DFA
303        matcher there was code that should only have been obeyed in UTF mode, but
304        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
305        processing when bytes with values greater than 127 were present. In 16-bit
306        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
307        both cases the values are those that cannot be the first data item in a UTF
308        character. The three items that might have provoked this were recursions,
309        possessively repeated groups, and atomic groups.
311    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
312        and pcregrep, because some OS require shared objects to be explicitly
313        passed to ld, causing the link step to fail if they are not.
315    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
316        mode, patterns that started with \h* or \R* might be incorrectly matched.
319    Version 8.30 04-February-2012
320    -----------------------------
322    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
323        name is defined in ctype.h.
325    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
326        only in quite long subpatterns.
328    3.  Removed the function pcre_info(), which has been obsolete and deprecated
329        since it was replaced by pcre_fullinfo() in February 2000.
331    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
332        match a (*MARK), and the match failed at the start of the subject, a
333        reference to memory before the start of the subject could occur. This bug
334        was introduced by fix 17 of release 8.21.
336    5.  A reference to an unset group with zero minimum repetition was giving
337        totally wrong answers (in non-JavaScript-compatibility mode). For example,
338        /(another)?(\1?)test/ matched against "hello world test". This bug was
339        introduced in release 8.13.
341    6.  Add support for 16-bit character strings (a large amount of work involving
342        many changes and refactorings).
344    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
345        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
346        from a file.
348    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
349        rounding is not applied in this particular case).
351    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
352        if they appear, or are escaped, in patterns.
354    10. Get rid of a number of -Wunused-but-set-variable warnings.
356    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
357        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
358        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
359        also returns the mark "x". This bug applied to capturing parentheses,
360        non-capturing parentheses, and atomic parentheses. It also applied to some
361        assertions.
363    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
364        information out of configure.ac instead of relying on pcre.h.generic, which
365        is not stored in the repository.
367    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
368        -lreadline.
370    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
372    15. Applied Graycode's patch to put the top-level frame on the stack rather
373        than the heap when not using the stack for recursion. This gives a
374        performance improvement in many cases when recursion is not deep.
376    16. Experimental code added to "pcretest -C" to output the stack frame size.
379    Version 8.21 12-Dec-2011
380    ------------------------
382  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
# Line 13  Version 8.21 Line 388  Version 8.21
388      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
389      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
391    4.  (*MARK) settings inside atomic groups that do not contain any capturing
392        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
393        was introduced by change 18 for 8.20.
395    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
396        ECMA-262 standard.
398    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
399        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
400        This bug was probably introduced by change 9 of 8.13.
402    7.  While fixing 6 above, I noticed that a number of other items were being
403        incorrectly rejected as "not fixed length". This arose partly because newer
404        opcodes had not been added to the fixed-length checking code. I have (a)
405        corrected the bug and added tests for these items, and (b) arranged for an
406        error to occur if an unknown opcode is encountered while checking for fixed
407        length instead of just assuming "not fixed length". The items that were
408        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
409        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
410        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
412    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
413        being incorrectly compiled and would have given unpredicatble results.
415    9.  A possessively repeated subpattern with minimum repeat count greater than
416        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
417        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
418        the first (A) could occur when it should not.
420    10. Add a cast and remove a redundant test from the code.
422    11. JIT should use pcre_malloc/pcre_free for allocation.
424    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
425        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
426        is anything other than /usr, -L is still shown).
428    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
430    14. Perl does not support \N without a following name in a [] class; PCRE now
431        also gives an error.
433    15. If a forward reference was repeated with an upper limit of around 2000,
434        it caused the error "internal error: overran compiling workspace". The
435        maximum number of forward references (including repeats) was limited by the
436        internal workspace, and dependent on the LINK_SIZE. The code has been
437        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
438        the default depends on LINK_SIZE. There is a new upper limit (for safety)
439        of around 200,000 forward references. While doing this, I also speeded up
440        the filling in of repeated forward references.
442    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
443        incorrectly expecting the subject to contain another "a" after the start.
445    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
446        in the match, the SKIP should be ignored. This was not happening; instead
447        the SKIP was being treated as NOMATCH. For patterns such as
448        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
449        tested.
451    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
452        now much more compatible with Perl, in particular in cases where the result
453        is a non-match for a non-anchored pattern. For example, if
454        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
455        "m", where previously it did not return a name. A side effect of this
456        change is that for partial matches, the last encountered mark name is
457        returned, as for non matches. A number of tests that were previously not
458        Perl-compatible have been moved into the Perl-compatible test files. The
459        refactoring has had the pleasing side effect of removing one argument from
460        the match() function, thus reducing its stack requirements.
462    19. If the /S+ option was used in pcretest to study a pattern using JIT,
463        subsequent uses of /S (without +) incorrectly behaved like /S+.
465    21. Retrieve executable code size support for the JIT compiler and fixing
466        some warnings.
468    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
469        not work when the shorter character appeared right at the end of the
470        subject string.
472    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
473        systems.
475    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
476        output it when the /M option is used in pcretest.
478    25. The CheckMan script was not being included in the distribution. Also, added
479        an explicit "perl" to run Perl scripts from the PrepareRelease script
480        because this is reportedly needed in Windows.
482    26. If study data was being save in a file and studying had not found a set of
483        "starts with" bytes for the pattern, the data written to the file (though
484        never used) was taken from uninitialized memory and so caused valgrind to
485        complain.
487    27. Updated RunTest.bat as provided by Sheri Pierce.
489    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
491    29. Computation of memory usage for the table of capturing group names was
492        giving an unnecessarily large value.
495  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
496  ------------------------  ------------------------

Removed from v.742  
changed lines
  Added in v.1221

  ViewVC Help
Powered by ViewVC 1.1.5