/[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 1314 by ph10, Fri Apr 26 10:44:13 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31  Version 8.33 xx-xxxx-201x
5    -------------------------
6    
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
11    
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
14    
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
18    
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
24    
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
28    
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
31    
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
34    
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
36    
37    9.  Optimizing fast_forward_start_bits in JIT.
38    
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
41    
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
43    
44        (b) Minimum length was not checked before the matching is started.
45    
46    11. The value of capture_last that is passed to callouts was incorrect in some
47        cases when there was a capture on one path that was subsequently abandoned
48        after a backtrack. Also, the capture_last value is now reset after a
49        recursion, since all captures are also reset in this case.
50    
51    12. The interpreter no longer returns the "too many substrings" error in the
52        case when an overflowing capture is in a branch that is subsequently
53        abandoned after a backtrack.
54    
55    13. In the pathological case when an offset vector of size 2 is used, pcretest
56        now prints out the matched string after a yield of 0 or 1.
57    
58    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
59        Only supported by the JIT compiler at the moment.
60    
61    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
62    
63    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
64        offset of the starting point of the matching process, provided the offsets
65        vector is large enough.
66    
67    17. The \A escape now records a lookbehind value of 1, though its execution
68        does not actually inspect the previous character. This is to ensure that,
69        in partial multi-segment matching, at least one character from the old
70        segment is retained when a new segment is processed. Otherwise, if there
71        are no lookbehinds in the pattern, \A might match incorrectly at the start
72        of a new segment.
73    
74    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
75    
76    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
77        gives some modest performance improvement in 8-bit mode.
78    
79    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
80        be expressed in certain programming languages using Universal Character
81        Names.
82    
83    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
84        which points out that "non characters" are not "characters that may not
85        appear in Unicode strings" but rather "characters that are reserved for
86        internal use and have only local meaning".
87    
88    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
89        there was a conditional group that depended on an assertion, if the
90        assertion was false, the callout that immediately followed the alternation
91        in the condition was skipped when pcre_exec() was used for matching.
92    
93    23. Allow an explicit callout to be inserted before an assertion that is the
94        condition for a conditional group, for compatibility with automatic
95        callouts, which always insert a callout at this point.
96    
97    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
98        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
99    
100    25. (*PRUNE) is now supported by the JIT compiler.
101    
102    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
103    
104    27. Fix the case where there are two or more SKIPs with arguments that may be
105        ignored.
106    
107    28. (*SKIP) is now supported by the JIT compiler.
108    
109    29. (*THEN) is now supported by the JIT compiler.
110    
111    30. Update RunTest with additional test selector options.
112    
113    31. The way PCRE handles backtracking verbs has been changed in two ways.
114    
115        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
116        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
117        backtracking. In some cases this makes it more Perl-compatible, but Perl's
118        rather obscure rules do not always do the same thing.
119    
120        (2) Previously, backtracking verbs were confined within assertions. This is
121        no longer the case for positive assertions, except for (*ACCEPT). Again,
122        this sometimes improves Perl compatibility, and sometimes does not.
123    
124    32. A number of tests that were in test 2 because Perl did things differently
125        have been moved to test 1, because either Perl or PCRE has changed, and
126        these tests are now compatible.
127    
128    32. Control verbs are handled in the same way in JIT and interpreter.
129    
130    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
131        contained a forward subroutine reference caused a compile error.
132    
133    34. Auto-detect and optimize limited repetitions in JIT.
134    
135    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
136        blocking (*UTF) etc.
137    
138    36. In the interpreter, maximizing pattern repetitions for characters and
139        character types now use tail recursion, which reduces stack usage.
140    
141    37. The value of the max lookbehind was not correctly preserved if a compiled
142        and saved regex was reloaded on a host of different endianness.
143    
144    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
145        of the compiled pattern block, expand the flags field from 16 to 32 bits
146        because it was almost full.
147    
148    
149    Version 8.32 30-November-2012
150  -----------------------------  -----------------------------
151    
152    1.  Improved JIT compiler optimizations for first character search and single
153        character iterators.
154    
155    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
156        Patch by Daniel Richard G.
157    
158    3.  Single character iterator optimizations in the JIT compiler.
159    
160    4.  Improved JIT compiler optimizations for character ranges.
161    
162    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
163        Reported by Giuseppe D'Angelo.
164    
165    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
166        of a line, was being set incorrectly in cases where .* appeared inside
167        atomic brackets at the start of a pattern, or where there was a subsequent
168        *PRUNE or *SKIP.
169    
170    7.  Improved instruction cache flush for POWER/PowerPC.
171        Patch by Daniel Richard G.
172    
173    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
174        grep:
175    
176        (a) There is now no limit to the number of patterns to be matched.
177    
178        (b) An error is given if a pattern is too long.
179    
180        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
181            are now supported.
182    
183        (d) --exclude-from and --include-from (multiple use) have been added.
184    
185        (e) Exclusions and inclusions now apply to all files and directories, not
186            just to those obtained from scanning a directory recursively.
187    
188        (f) Multiple uses of -f and --file-list are now supported.
189    
190        (g) In a Windows environment, the default for -d has been changed from
191            "read" (the GNU grep default) to "skip", because otherwise the presence
192            of a directory in the file list provokes an error.
193    
194        (h) The documentation has been revised and clarified in places.
195    
196    9.  Improve the matching speed of capturing brackets.
197    
198    10. Changed the meaning of \X so that it now matches a Unicode extended
199        grapheme cluster.
200    
201    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
202        out POSIX threads when JIT support is configured.
203    
204    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
205    
206    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
207        structure could go wrong in environments where size_t is not the same size
208        as int.
209    
210    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
211        set.
212    
213    15. The EBCDIC support had decayed; later updates to the code had included
214        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
215        general tidy up of EBCDIC-related issues, and the documentation was also
216        not quite right. There is now a test that can be run on ASCII systems to
217        check some of the EBCDIC-related things (but is it not a full test).
218    
219    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
220        in a small tidy to the code.
221    
222    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
223    
224    18. If the --only-matching (-o) option in pcregrep is specified multiple
225        times, each one causes appropriate output. For example, -o1 -o2 outputs the
226        substrings matched by the 1st and 2nd capturing parentheses. A separating
227        string can be specified by --om-separator (default empty).
228    
229    19. Improving the first n character searches.
230    
231    20. Turn case lists for horizontal and vertical white space into macros so that
232        they are defined only once.
233    
234    21. This set of changes together give more compatible Unicode case-folding
235        behaviour for characters that have more than one other case when UCP
236        support is available.
237    
238        (a) The Unicode property table now has offsets into a new table of sets of
239            three or more characters that are case-equivalent. The MultiStage2.py
240            script that generates these tables (the pcre_ucd.c file) now scans
241            CaseFolding.txt instead of UnicodeData.txt for character case
242            information.
243    
244        (b) The code for adding characters or ranges of characters to a character
245            class has been abstracted into a generalized function that also handles
246            case-independence. In UTF-mode with UCP support, this uses the new data
247            to handle characters with more than one other case.
248    
249        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
250            whose other case is greater than 256 are now correctly matched
251            caselessly. Previously, the high codepoint matched the low one, but not
252            vice versa.
253    
254        (d) The processing of \h, \H, \v, and \ in character classes now makes use
255            of the new class addition function, using character lists defined as
256            macros alongside the case definitions of 20 above.
257    
258        (e) Caseless back references now work with characters that have more than
259            one other case.
260    
261        (f) General caseless matching of characters with more than one other case
262            is supported.
263    
264    22. Unicode character properties were updated from Unicode 6.2.0
265    
266    23. Improved CMake support under Windows. Patch by Daniel Richard G.
267    
268    24. Add support for 32-bit character strings, and UTF-32
269    
270    25. Major JIT compiler update (code refactoring and bugfixing).
271        Experimental Sparc 32 support is added.
272    
273    26. Applied a modified version of Daniel Richard G's patch to create
274        pcre.h.generic and config.h.generic by "make" instead of in the
275        PrepareRelease script.
276    
277    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
278        pcre_compile.c when checking for a zero character.
279    
280    28. Introducing a native interface for JIT. Through this interface, the compiled
281        machine code can be directly executed. The purpose of this interface is to
282        provide fast pattern matching, so several sanity checks are not performed.
283        However, feature tests are still performed. The new interface provides
284        1.4x speedup compared to the old one.
285    
286    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
287        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
288        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
289    
290    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
291        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
292        the "old" RFC 2279). Instead, it ended up passing a negative length to
293        pcre_exec().
294    
295    31. Add support for GCC's visibility feature to hide internal functions.
296    
297    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
298        "unknown -C option" after outputting 0 or 1.
299    
300    33. There is now support for generating a code coverage report for the test
301        suite in environments where gcc is the compiler and lcov is installed. This
302        is mainly for the benefit of the developers.
303    
304    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
305        unaddressable using valgrind annotations, allowing valgrind to detect
306        invalid memory accesses. This is mainly for the benefit of the developers.
307    
308    25. (*UTF) can now be used to start a pattern in any of the three libraries.
309    
310    26. Give configure error if --enable-cpp but no C++ compiler found.
311    
312    
313    Version 8.31 06-July-2012
314    -------------------------
315    
316  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
317    
318  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
# Line 95  Version 8.31 Line 404  Version 8.31
404      \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.
405      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
406      lookup were testing for characters less than 127 instead of 255.      lookup were testing for characters less than 127 instead of 255.
407    
408  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,
409      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
410      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
411      there were back references that the ovector was too small to contain      there were back references that the ovector was too small to contain
412      (causing temporary malloc'd memory to be used during matching), and the      (causing temporary malloc'd memory to be used during matching), and the
413      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
414      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
415      memory instead of the true size.)      memory instead of the true size.)
416    
417  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
418      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.
419    
420  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
421      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.
422    
423  30. JIT compiler update.  30. JIT compiler update.
# Line 120  Version 8.31 Line 429  Version 8.31
429    
430  33. Variable renamings in the PCRE-JIT compiler. No functionality change.  33. Variable renamings in the PCRE-JIT compiler. No functionality change.
431    
432  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
433      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)
434      was enabled.      was enabled.
435    
436  35. Improve JIT code generation for greedy plus quantifier.  35. Improve JIT code generation for greedy plus quantifier.
437    
438    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
439        1 to "aa" instead of to an empty string. The bug affected repeated groups
440        that could potentially match an empty string.
441    
442    37. Optimizing single character iterators in JIT.
443    
444    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
445        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
446        codepoints that are too big for the mode are faulted, and in a UTF mode,
447        disallowed codepoints are also faulted.
448    
449    39. If PCRE was compiled with UTF support, in three places in the DFA
450        matcher there was code that should only have been obeyed in UTF mode, but
451        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
452        processing when bytes with values greater than 127 were present. In 16-bit
453        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
454        both cases the values are those that cannot be the first data item in a UTF
455        character. The three items that might have provoked this were recursions,
456        possessively repeated groups, and atomic groups.
457    
458    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
459        and pcregrep, because some OS require shared objects to be explicitly
460        passed to ld, causing the link step to fail if they are not.
461    
462    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
463        mode, patterns that started with \h* or \R* might be incorrectly matched.
464    
465    
466  Version 8.30 04-February-2012  Version 8.30 04-February-2012
467  -----------------------------  -----------------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5