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

Diff of /code/trunk/ChangeLog

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

revision 974 by zherczeg, Sat Jun 2 05:56:58 2012 UTC revision 994 by ph10, Tue Jul 10 14:29:26 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    
26    Version 8.31 06-July-2012
27    -------------------------
28    
29  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
30    
# Line 95  Version 8.31 Line 117  Version 8.31
117      \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.
118      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
119      lookup were testing for characters less than 127 instead of 255.      lookup were testing for characters less than 127 instead of 255.
120    
121  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,
122      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
123      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
124      there were back references that the ovector was too small to contain      there were back references that the ovector was too small to contain
125      (causing temporary malloc'd memory to be used during matching), and the      (causing temporary malloc'd memory to be used during matching), and the
126      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
127      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
128      memory instead of the true size.)      memory instead of the true size.)
129    
130  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
131      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.
132    
133  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
134      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.
135    
136  30. JIT compiler update.  30. JIT compiler update.
# Line 120  Version 8.31 Line 142  Version 8.31
142    
143  33. Variable renamings in the PCRE-JIT compiler. No functionality change.  33. Variable renamings in the PCRE-JIT compiler. No functionality change.
144    
145  34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of  34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
146      SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)      SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
147      was enabled.      was enabled.
148    
149  35. Improve JIT code generation for greedy plus quantifier.  35. Improve JIT code generation for greedy plus quantifier.
150    
151    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
152        1 to "aa" instead of to an empty string. The bug affected repeated groups
153        that could potentially match an empty string.
154    
155    37. Optimizing single character iterators in JIT.
156    
157    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
158        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
159        codepoints that are too big for the mode are faulted, and in a UTF mode,
160        disallowed codepoints are also faulted.
161    
162    39. If PCRE was compiled with UTF support, in three places in the DFA
163        matcher there was code that should only have been obeyed in UTF mode, but
164        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
165        processing when bytes with values greater than 127 were present. In 16-bit
166        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
167        both cases the values are those that cannot be the first data item in a UTF
168        character. The three items that might have provoked this were recursions,
169        possessively repeated groups, and atomic groups.
170    
171    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
172        and pcregrep, because some OS require shared objects to be explicitly
173        passed to ld, causing the link step to fail if they are not.
174    
175    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
176        mode, patterns that started with \h* or \R* might be incorrectly matched.
177    
178    
179  Version 8.30 04-February-2012  Version 8.30 04-February-2012
180  -----------------------------  -----------------------------

Legend:
Removed from v.974  
changed lines
  Added in v.994

  ViewVC Help
Powered by ViewVC 1.1.5