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 |
|
|
54 |
|
Version 8.31 06-July-2012 |
55 |
|
------------------------- |
56 |
|
|
57 |
1. Fixing a wrong JIT test case and some compiler warnings. |
1. Fixing a wrong JIT test case and some compiler warnings. |
58 |
|
|
145 |
\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. |
146 |
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 |
147 |
lookup were testing for characters less than 127 instead of 255. |
lookup were testing for characters less than 127 instead of 255. |
148 |
|
|
149 |
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, |
150 |
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 |
151 |
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 |
152 |
there were back references that the ovector was too small to contain |
there were back references that the ovector was too small to contain |
153 |
(causing temporary malloc'd memory to be used during matching), and the |
(causing temporary malloc'd memory to be used during matching), and the |
154 |
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 |
155 |
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 |
156 |
memory instead of the true size.) |
memory instead of the true size.) |
157 |
|
|
158 |
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 |
159 |
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. |
160 |
|
|
161 |
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 |
162 |
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. |
163 |
|
|
164 |
30. JIT compiler update. |
30. JIT compiler update. |
170 |
|
|
171 |
33. Variable renamings in the PCRE-JIT compiler. No functionality change. |
33. Variable renamings in the PCRE-JIT compiler. No functionality change. |
172 |
|
|
173 |
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 |
174 |
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) |
175 |
was enabled. |
was enabled. |
176 |
|
|
177 |
35. Improve JIT code generation for greedy plus quantifier. |
35. Improve JIT code generation for greedy plus quantifier. |
178 |
|
|
179 |
|
36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group |
180 |
|
1 to "aa" instead of to an empty string. The bug affected repeated groups |
181 |
|
that could potentially match an empty string. |
182 |
|
|
183 |
|
37. Optimizing single character iterators in JIT. |
184 |
|
|
185 |
|
38. Wide characters specified with \uxxxx in JavaScript mode are now subject to |
186 |
|
the same checks as \x{...} characters in non-JavaScript mode. Specifically, |
187 |
|
codepoints that are too big for the mode are faulted, and in a UTF mode, |
188 |
|
disallowed codepoints are also faulted. |
189 |
|
|
190 |
|
39. If PCRE was compiled with UTF support, in three places in the DFA |
191 |
|
matcher there was code that should only have been obeyed in UTF mode, but |
192 |
|
was being obeyed unconditionally. In 8-bit mode this could cause incorrect |
193 |
|
processing when bytes with values greater than 127 were present. In 16-bit |
194 |
|
mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In |
195 |
|
both cases the values are those that cannot be the first data item in a UTF |
196 |
|
character. The three items that might have provoked this were recursions, |
197 |
|
possessively repeated groups, and atomic groups. |
198 |
|
|
199 |
|
40. Ensure that libpcre is explicitly listed in the link commands for pcretest |
200 |
|
and pcregrep, because some OS require shared objects to be explicitly |
201 |
|
passed to ld, causing the link step to fail if they are not. |
202 |
|
|
203 |
|
41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit |
204 |
|
mode, patterns that started with \h* or \R* might be incorrectly matched. |
205 |
|
|
206 |
|
|
207 |
Version 8.30 04-February-2012 |
Version 8.30 04-February-2012 |
208 |
----------------------------- |
----------------------------- |