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

Diff of /code/trunk/ChangeLog

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

revision 967 by zherczeg, Mon May 14 07:36:39 2012 UTC revision 1266 by ph10, Sun Mar 3 11:14:26 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    
98    Version 8.32 30-November-2012
99  -----------------------------  -----------------------------
100    
101    1.  Improved JIT compiler optimizations for first character search and single
102        character iterators.
103    
104    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
105        Patch by Daniel Richard G.
106    
107    3.  Single character iterator optimizations in the JIT compiler.
108    
109    4.  Improved JIT compiler optimizations for character ranges.
110    
111    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
112        Reported by Giuseppe D'Angelo.
113    
114    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
115        of a line, was being set incorrectly in cases where .* appeared inside
116        atomic brackets at the start of a pattern, or where there was a subsequent
117        *PRUNE or *SKIP.
118    
119    7.  Improved instruction cache flush for POWER/PowerPC.
120        Patch by Daniel Richard G.
121    
122    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
123        grep:
124    
125        (a) There is now no limit to the number of patterns to be matched.
126    
127        (b) An error is given if a pattern is too long.
128    
129        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
130            are now supported.
131    
132        (d) --exclude-from and --include-from (multiple use) have been added.
133    
134        (e) Exclusions and inclusions now apply to all files and directories, not
135            just to those obtained from scanning a directory recursively.
136    
137        (f) Multiple uses of -f and --file-list are now supported.
138    
139        (g) In a Windows environment, the default for -d has been changed from
140            "read" (the GNU grep default) to "skip", because otherwise the presence
141            of a directory in the file list provokes an error.
142    
143        (h) The documentation has been revised and clarified in places.
144    
145    9.  Improve the matching speed of capturing brackets.
146    
147    10. Changed the meaning of \X so that it now matches a Unicode extended
148        grapheme cluster.
149    
150    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
151        out POSIX threads when JIT support is configured.
152    
153    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
154    
155    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
156        structure could go wrong in environments where size_t is not the same size
157        as int.
158    
159    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
160        set.
161    
162    15. The EBCDIC support had decayed; later updates to the code had included
163        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
164        general tidy up of EBCDIC-related issues, and the documentation was also
165        not quite right. There is now a test that can be run on ASCII systems to
166        check some of the EBCDIC-related things (but is it not a full test).
167    
168    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
169        in a small tidy to the code.
170    
171    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
172    
173    18. If the --only-matching (-o) option in pcregrep is specified multiple
174        times, each one causes appropriate output. For example, -o1 -o2 outputs the
175        substrings matched by the 1st and 2nd capturing parentheses. A separating
176        string can be specified by --om-separator (default empty).
177    
178    19. Improving the first n character searches.
179    
180    20. Turn case lists for horizontal and vertical white space into macros so that
181        they are defined only once.
182    
183    21. This set of changes together give more compatible Unicode case-folding
184        behaviour for characters that have more than one other case when UCP
185        support is available.
186    
187        (a) The Unicode property table now has offsets into a new table of sets of
188            three or more characters that are case-equivalent. The MultiStage2.py
189            script that generates these tables (the pcre_ucd.c file) now scans
190            CaseFolding.txt instead of UnicodeData.txt for character case
191            information.
192    
193        (b) The code for adding characters or ranges of characters to a character
194            class has been abstracted into a generalized function that also handles
195            case-independence. In UTF-mode with UCP support, this uses the new data
196            to handle characters with more than one other case.
197    
198        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
199            whose other case is greater than 256 are now correctly matched
200            caselessly. Previously, the high codepoint matched the low one, but not
201            vice versa.
202    
203        (d) The processing of \h, \H, \v, and \ in character classes now makes use
204            of the new class addition function, using character lists defined as
205            macros alongside the case definitions of 20 above.
206    
207        (e) Caseless back references now work with characters that have more than
208            one other case.
209    
210        (f) General caseless matching of characters with more than one other case
211            is supported.
212    
213    22. Unicode character properties were updated from Unicode 6.2.0
214    
215    23. Improved CMake support under Windows. Patch by Daniel Richard G.
216    
217    24. Add support for 32-bit character strings, and UTF-32
218    
219    25. Major JIT compiler update (code refactoring and bugfixing).
220        Experimental Sparc 32 support is added.
221    
222    26. Applied a modified version of Daniel Richard G's patch to create
223        pcre.h.generic and config.h.generic by "make" instead of in the
224        PrepareRelease script.
225    
226    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
227        pcre_compile.c when checking for a zero character.
228    
229    28. Introducing a native interface for JIT. Through this interface, the compiled
230        machine code can be directly executed. The purpose of this interface is to
231        provide fast pattern matching, so several sanity checks are not performed.
232        However, feature tests are still performed. The new interface provides
233        1.4x speedup compared to the old one.
234    
235    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
236        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
237        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
238    
239    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
240        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
241        the "old" RFC 2279). Instead, it ended up passing a negative length to
242        pcre_exec().
243    
244    31. Add support for GCC's visibility feature to hide internal functions.
245    
246    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
247        "unknown -C option" after outputting 0 or 1.
248    
249    33. There is now support for generating a code coverage report for the test
250        suite in environments where gcc is the compiler and lcov is installed. This
251        is mainly for the benefit of the developers.
252    
253    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
254        unaddressable using valgrind annotations, allowing valgrind to detect
255        invalid memory accesses. This is mainly for the benefit of the developers.
256    
257    25. (*UTF) can now be used to start a pattern in any of the three libraries.
258    
259    26. Give configure error if --enable-cpp but no C++ compiler found.
260    
261    
262    Version 8.31 06-July-2012
263    -------------------------
264    
265  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
266    
267  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
# Line 95  Version 8.31 Line 353  Version 8.31
353      \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.
354      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
355      lookup were testing for characters less than 127 instead of 255.      lookup were testing for characters less than 127 instead of 255.
356    
357  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,
358      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
359      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
360      there were back references that the ovector was too small to contain      there were back references that the ovector was too small to contain
361      (causing temporary malloc'd memory to be used during matching), and the      (causing temporary malloc'd memory to be used during matching), and the
362      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
363      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
364      memory instead of the true size.)      memory instead of the true size.)
365    
366  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
367      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.
368    
369  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
370      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.
371    
372  30. JIT compiler update.  30. JIT compiler update.
# Line 116  Version 8.31 Line 374  Version 8.31
374  31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger  31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
375      Rill for the patch.      Rill for the patch.
376    
377    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
378    
379    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
380    
381    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
382        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
383        was enabled.
384    
385    35. Improve JIT code generation for greedy plus quantifier.
386    
387    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
388        1 to "aa" instead of to an empty string. The bug affected repeated groups
389        that could potentially match an empty string.
390    
391    37. Optimizing single character iterators in JIT.
392    
393    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
394        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
395        codepoints that are too big for the mode are faulted, and in a UTF mode,
396        disallowed codepoints are also faulted.
397    
398    39. If PCRE was compiled with UTF support, in three places in the DFA
399        matcher there was code that should only have been obeyed in UTF mode, but
400        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
401        processing when bytes with values greater than 127 were present. In 16-bit
402        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
403        both cases the values are those that cannot be the first data item in a UTF
404        character. The three items that might have provoked this were recursions,
405        possessively repeated groups, and atomic groups.
406    
407    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
408        and pcregrep, because some OS require shared objects to be explicitly
409        passed to ld, causing the link step to fail if they are not.
410    
411    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
412        mode, patterns that started with \h* or \R* might be incorrectly matched.
413    
414    
415  Version 8.30 04-February-2012  Version 8.30 04-February-2012
416  -----------------------------  -----------------------------

Legend:
Removed from v.967  
changed lines
  Added in v.1266

  ViewVC Help
Powered by ViewVC 1.1.5