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

Diff of /code/trunk/ChangeLog

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

revision 942 by ph10, Tue Feb 28 14:50:31 2012 UTC revision 1219 by ph10, Sun Nov 11 18:04:37 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31  Version 8.32 11-November-2012
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    20. Turn case lists for horizontal and vertical white space into macros so that
87        they are defined only once.
88    
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.
92    
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.
98    
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.
103    
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.
108    
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.
112    
113        (e) Caseless back references now work with characters that have more than
114            one other case.
115    
116        (f) General caseless matching of characters with more than one other case
117            is supported.
118    
119    22. Unicode character properties were updated from Unicode 6.2.0
120    
121    23. Improved CMake support under Windows. Patch by Daniel Richard G.
122    
123    24. Add support for 32-bit character strings, and UTF-32
124    
125    25. Major JIT compiler update (code refactoring and bugfixing).
126        Experimental Sparc 32 support is added.
127    
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.
131    
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.
134    
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.
140    
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.
144    
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().
149    
150    31. Add support for GCC's visibility feature to hide internal functions.
151    
152    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
153        "unknown -C option" after outputting 0 or 1.
154    
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.
158    
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.
162    
163    25. (*UTF) can now be used to start a pattern in any of the three libraries.
164    
165    
166    Version 8.31 06-July-2012
167    -------------------------
168    
169  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
170    
171  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
172    
173  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied  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      to unsigned type, result still unsigned" that was given by an MS compiler
175      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
176    
177  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
# Line 18  Version 8.31 Line 180  Version 8.31
180      of more than one character:      of more than one character:
181    
182      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
183          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
184          references.          references.
185    
186      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
187          subject.          subject.
188    
189      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
190          characters at the end of the subject.          characters at the end of the subject.
191    
192      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
# Line 33  Version 8.31 Line 195  Version 8.31
195      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (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.          a partial match for a CR character at the end of the subject string.
197    
198  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when  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      running pcretest, the text "(JIT)" added to the output whenever JIT is
200      actually used to run the match.      actually used to run the match.
201    
202  7.  Individual JIT compile options can be set in pcretest by following -s+[+]  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
203      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
204    
205  8.  OP_NOT now supports any UTF character not just single-byte ones.  8.  OP_NOT now supports any UTF character not just single-byte ones.
# Line 46  Version 8.31 Line 208  Version 8.31
208    
209  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
210      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
211    
212  11. Add PCRE_INFO_MAXLOOKBEHIND.  11. Add PCRE_INFO_MAXLOOKBEHIND.
213    
214  12. Applied a (slightly modified) user-supplied patch that improves performance  12. Applied a (slightly modified) user-supplied patch that improves performance
215      when the heap is used for recursion (compiled with --disable-stack-for-      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      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      logical recursion happens, frames are retained on a chain and re-used where
218      possible. This sometimes gives as much as 30% improvement.      possible. This sometimes gives as much as 30% improvement.
219    
220  13. As documented, (*COMMIT) is now confined to within a recursive subpattern  13. As documented, (*COMMIT) is now confined to within a recursive subpattern
221      call.      call.
222    
223  14. As documented, (*COMMIT) is now confined to within a positive assertion.  14. As documented, (*COMMIT) is now confined to within a positive assertion.
224    
225  15. It is now possible to link pcretest with libedit as an alternative to  15. It is now possible to link pcretest with libedit as an alternative to
226      libreadline.      libreadline.
227    
228  16. (*COMMIT) control verb is now supported by the JIT compiler.  16. (*COMMIT) control verb is now supported by the JIT compiler.
229    
230  6.  The Unicode data tables have been updated to Unicode 6.1.0.  17. The Unicode data tables have been updated to Unicode 6.1.0.
231    
232    18. Added --file-list option to pcregrep.
233    
234    19. Added binary file support to pcregrep, including the -a, --binary-files,
235        -I, and --text options.
236    
237    20. The madvise function is renamed for posix_madvise for QNX compatibility
238        reasons. Fixed by Giuseppe D'Angelo.
239    
240    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
241    
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.
244    
245    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
246    
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.
251    
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).
255    
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.
260    
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.)
269    
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.
272    
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.
275    
276    30. JIT compiler update.
277    
278    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
279        Rill for the patch.
280    
281    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
282    
283    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
284    
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.
288    
289    35. Improve JIT code generation for greedy plus quantifier.
290    
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.
294    
295    37. Optimizing single character iterators in JIT.
296    
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.
301    
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.
310    
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.
314    
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.
317    
318    
319  Version 8.30 04-February-2012  Version 8.30 04-February-2012

Legend:
Removed from v.942  
changed lines
  Added in v.1219

  ViewVC Help
Powered by ViewVC 1.1.5