ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 909 by ph10, Sat Feb 4 15:01:47 2012 UTC revision 1045 by ph10, Sun Sep 23 16:50:00 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 8.32
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.
92        (a) The Unicode property table now has offsets into a new table of sets of
93            three or more characters that are case-equivalent. The MultiStage2.py
94            script that generates these tables (the pcre_ucd.c file) now scans
95            CaseFolding.txt instead of UnicodeData.txt for character case
96            information.
98        (b) The code for adding characters or ranges of characters to a character
99            class has been abstracted into a generalized function that also handles
100            case-independence. In UTF-mode with UCP support, this uses the new data
101            to handle characters with more than one other case.
103        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
104            whose other case is greater than 256 are now correctly matched
105            caselessly. Previously, the high codepoint matched the low one, but not
106            vice versa.
108        (d) The processing of \h, \H, \v, and \ in character classes now makes use
109            of the new class addition function, using character lists defined as
110            macros alongside the case definitions of 20 above.
113    Version 8.31 06-July-2012
114    -------------------------
116    1.  Fixing a wrong JIT test case and some compiler warnings.
118    2.  Removed a bashism from the RunTest script.
120    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
121        to unsigned type, result still unsigned" that was given by an MS compiler
122        on encountering the code "-sizeof(xxx)".
124    4.  Partial matching support is added to the JIT compiler.
126    5.  Fixed several bugs concerned with partial matching of items that consist
127        of more than one character:
129        (a) /^(..)\1/ did not partially match "aba" because checking references was
130            done on an "all or nothing" basis. This also applied to repeated
131            references.
133        (b) \R did not give a hard partial match if \r was found at the end of the
134            subject.
136        (c) \X did not give a hard partial match after matching one or more
137            characters at the end of the subject.
139        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
140            a partial match for the string "\r".
142        (e) When newline was set to CRLF, the metacharacter "." did not recognize
143            a partial match for a CR character at the end of the subject string.
145    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
146        running pcretest, the text "(JIT)" added to the output whenever JIT is
147        actually used to run the match.
149    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
150        or /S+[+] with a digit between 1 and 7.
152    8.  OP_NOT now supports any UTF character not just single-byte ones.
154    9.  (*MARK) control verb is now supported by the JIT compiler.
156    10. The command "./RunTest list" lists the available tests without actually
157        running any of them. (Because I keep forgetting what they all are.)
161    12. Applied a (slightly modified) user-supplied patch that improves performance
162        when the heap is used for recursion (compiled with --disable-stack-for-
163        recursion). Instead of malloc and free for each heap frame each time a
164        logical recursion happens, frames are retained on a chain and re-used where
165        possible. This sometimes gives as much as 30% improvement.
167    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
168        call.
170    14. As documented, (*COMMIT) is now confined to within a positive assertion.
172    15. It is now possible to link pcretest with libedit as an alternative to
173        libreadline.
175    16. (*COMMIT) control verb is now supported by the JIT compiler.
177    17. The Unicode data tables have been updated to Unicode 6.1.0.
179    18. Added --file-list option to pcregrep.
181    19. Added binary file support to pcregrep, including the -a, --binary-files,
182        -I, and --text options.
184    20. The madvise function is renamed for posix_madvise for QNX compatibility
185        reasons. Fixed by Giuseppe D'Angelo.
187    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
189    22. Changed the option for creating symbolic links for 16-bit man pages from
190        -s to -sf so that re-installing does not cause issues.
192    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
194    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
195        matches in certain environments (the workspace was not being correctly
196        retained). Also added to pcre_dfa_exec() a simple plausibility check on
197        some of the workspace data at the beginning of a restart.
199    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
200        was not doing so when it should - probably a typo introduced by SVN 528
201        (change 8.10/14).
203    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
204        \w+ when the character tables indicated that \x{c4} was a word character.
205        There were several related cases, all because the tests for doing a table
206        lookup were testing for characters less than 127 instead of 255.
208    27. If a pattern contains capturing parentheses that are not used in a match,
209        their slots in the ovector are set to -1. For those that are higher than
210        any matched groups, this happens at the end of processing. In the case when
211        there were back references that the ovector was too small to contain
212        (causing temporary malloc'd memory to be used during matching), and the
213        highest capturing number was not used, memory off the end of the ovector
214        was incorrectly being set to -1. (It was using the size of the temporary
215        memory instead of the true size.)
217    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
218        ovector size, it uses memory at the end of the block that it has got.
220    29. Check for an overlong MARK name and give an error at compile time. The
221        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
223    30. JIT compiler update.
225    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
226        Rill for the patch.
228    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
230    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
232    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
233        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
234        was enabled.
236    35. Improve JIT code generation for greedy plus quantifier.
238    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
239        1 to "aa" instead of to an empty string. The bug affected repeated groups
240        that could potentially match an empty string.
242    37. Optimizing single character iterators in JIT.
244    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
245        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
246        codepoints that are too big for the mode are faulted, and in a UTF mode,
247        disallowed codepoints are also faulted.
249    39. If PCRE was compiled with UTF support, in three places in the DFA
250        matcher there was code that should only have been obeyed in UTF mode, but
251        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
252        processing when bytes with values greater than 127 were present. In 16-bit
253        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
254        both cases the values are those that cannot be the first data item in a UTF
255        character. The three items that might have provoked this were recursions,
256        possessively repeated groups, and atomic groups.
258    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
259        and pcregrep, because some OS require shared objects to be explicitly
260        passed to ld, causing the link step to fail if they are not.
262    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
263        mode, patterns that started with \h* or \R* might be incorrectly matched.
266  Version 8.30 04-February-2012  Version 8.30 04-February-2012
267  -----------------------------  -----------------------------

Removed from v.909  
changed lines
  Added in v.1045

  ViewVC Help
Powered by ViewVC 1.1.5