/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 964 by ph10, Fri May 4 13:03:39 2012 UTC revision 1040 by zherczeg, Sun Sep 16 06:52:27 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31  Version 8.32
5  -----------------------------  ------------
6    
7    1.  Improved JIT compiler optimizations for first character search and single
8        character iterators.
9    
10    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
11        Patch by Daniel Richard G.
12    
13    3.  Single character iterator optimizations in the JIT compiler.
14    
15    4.  Improved JIT compiler optimizations for character ranges.
16    
17    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
18        Reported by Giuseppe D'Angelo.
19    
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.
24    
25    7.  Improved instruction cache flush for POWER/PowerPC.
26        Patch by Daniel Richard G.
27    
28    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
29        grep:
30    
31        (a) There is now no limit to the number of patterns to be matched.
32    
33        (b) An error is given if a pattern is too long.
34    
35        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
36            are now supported.
37    
38        (d) --exclude-from and --include-from (multiple use) have been added.
39    
40        (e) Exclusions and inclusions now apply to all files and directories, not
41            just to those obtained from scanning a directory recursively.
42    
43        (f) Multiple uses of -f and --file-list are now supported.
44    
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.
48    
49        (h) The documentation has been revised and clarified in places.
50    
51    9.  Improve the matching speed of capturing brackets.
52    
53    10. Changed the meaning of \X so that it now matches a Unicode extended
54        grapheme cluster.
55    
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.
58    
59    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
60    
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.
64    
65    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
66        set.
67    
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).
73    
74    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
75        in a small tidy to the code.
76    
77    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
78    
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).
83    
84    19. Improving the first n character searches.
85    
86    
87    Version 8.31 06-July-2012
88    -------------------------
89    
90  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
91    
# Line 95  Version 8.31 Line 178  Version 8.31
178      \w+ when the character tables indicated that \x{c4} was a word character.      \w+ when the character tables indicated that \x{c4} was a word character.
179      There were several related cases, all because the tests for doing a table      There were several related cases, all because the tests for doing a table
180      lookup were testing for characters less than 127 instead of 255.      lookup were testing for characters less than 127 instead of 255.
181    
182  27. If a pattern contains capturing parentheses that are not used in a match,  27. If a pattern contains capturing parentheses that are not used in a match,
183      their slots in the ovector are set to -1. For those that are higher than      their slots in the ovector are set to -1. For those that are higher than
184      any matched groups, this happens at the end of processing. In the case when      any matched groups, this happens at the end of processing. In the case when
185      there were back references that the ovector was too small to contain      there were back references that the ovector was too small to contain
186      (causing temporary malloc'd memory to be used during matching), and the      (causing temporary malloc'd memory to be used during matching), and the
187      highest capturing number was not used, memory off the end of the ovector      highest capturing number was not used, memory off the end of the ovector
188      was incorrectly being set to -1. (It was using the size of the temporary      was incorrectly being set to -1. (It was using the size of the temporary
189      memory instead of the true size.)      memory instead of the true size.)
190    
191  28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an  28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
192      ovector size, it uses memory at the end of the block that it has got.      ovector size, it uses memory at the end of the block that it has got.
193    
194  29. Check for an overlong MARK name and give an error at compile time. The  29. Check for an overlong MARK name and give an error at compile time. The
195      limit is 255 for the 8-bit library and 65535 for the 16-bit library.      limit is 255 for the 8-bit library and 65535 for the 16-bit library.
196    
197    30. JIT compiler update.
198    
199    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
200        Rill for the patch.
201    
202    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
203    
204    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
205    
206    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
207        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
208        was enabled.
209    
210    35. Improve JIT code generation for greedy plus quantifier.
211    
212    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
213        1 to "aa" instead of to an empty string. The bug affected repeated groups
214        that could potentially match an empty string.
215    
216    37. Optimizing single character iterators in JIT.
217    
218    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
219        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
220        codepoints that are too big for the mode are faulted, and in a UTF mode,
221        disallowed codepoints are also faulted.
222    
223    39. If PCRE was compiled with UTF support, in three places in the DFA
224        matcher there was code that should only have been obeyed in UTF mode, but
225        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
226        processing when bytes with values greater than 127 were present. In 16-bit
227        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
228        both cases the values are those that cannot be the first data item in a UTF
229        character. The three items that might have provoked this were recursions,
230        possessively repeated groups, and atomic groups.
231    
232    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
233        and pcregrep, because some OS require shared objects to be explicitly
234        passed to ld, causing the link step to fail if they are not.
235    
236    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
237        mode, patterns that started with \h* or \R* might be incorrectly matched.
238    
239    
240  Version 8.30 04-February-2012  Version 8.30 04-February-2012
241  -----------------------------  -----------------------------

Legend:
Removed from v.964  
changed lines
  Added in v.1040

  ViewVC Help
Powered by ViewVC 1.1.5