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

Diff of /code/trunk/ChangeLog

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

revision 933 by ph10, Sat Feb 25 12:18:23 2012 UTC revision 1250 by zherczeg, Wed Feb 20 09:59:29 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    
64    Version 8.32 30-November-2012
65  -----------------------------  -----------------------------
66    
67    1.  Improved JIT compiler optimizations for first character search and single
68        character iterators.
69    
70    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
71        Patch by Daniel Richard G.
72    
73    3.  Single character iterator optimizations in the JIT compiler.
74    
75    4.  Improved JIT compiler optimizations for character ranges.
76    
77    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
78        Reported by Giuseppe D'Angelo.
79    
80    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
81        of a line, was being set incorrectly in cases where .* appeared inside
82        atomic brackets at the start of a pattern, or where there was a subsequent
83        *PRUNE or *SKIP.
84    
85    7.  Improved instruction cache flush for POWER/PowerPC.
86        Patch by Daniel Richard G.
87    
88    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
89        grep:
90    
91        (a) There is now no limit to the number of patterns to be matched.
92    
93        (b) An error is given if a pattern is too long.
94    
95        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
96            are now supported.
97    
98        (d) --exclude-from and --include-from (multiple use) have been added.
99    
100        (e) Exclusions and inclusions now apply to all files and directories, not
101            just to those obtained from scanning a directory recursively.
102    
103        (f) Multiple uses of -f and --file-list are now supported.
104    
105        (g) In a Windows environment, the default for -d has been changed from
106            "read" (the GNU grep default) to "skip", because otherwise the presence
107            of a directory in the file list provokes an error.
108    
109        (h) The documentation has been revised and clarified in places.
110    
111    9.  Improve the matching speed of capturing brackets.
112    
113    10. Changed the meaning of \X so that it now matches a Unicode extended
114        grapheme cluster.
115    
116    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
117        out POSIX threads when JIT support is configured.
118    
119    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
120    
121    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
122        structure could go wrong in environments where size_t is not the same size
123        as int.
124    
125    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
126        set.
127    
128    15. The EBCDIC support had decayed; later updates to the code had included
129        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
130        general tidy up of EBCDIC-related issues, and the documentation was also
131        not quite right. There is now a test that can be run on ASCII systems to
132        check some of the EBCDIC-related things (but is it not a full test).
133    
134    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
135        in a small tidy to the code.
136    
137    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
138    
139    18. If the --only-matching (-o) option in pcregrep is specified multiple
140        times, each one causes appropriate output. For example, -o1 -o2 outputs the
141        substrings matched by the 1st and 2nd capturing parentheses. A separating
142        string can be specified by --om-separator (default empty).
143    
144    19. Improving the first n character searches.
145    
146    20. Turn case lists for horizontal and vertical white space into macros so that
147        they are defined only once.
148    
149    21. This set of changes together give more compatible Unicode case-folding
150        behaviour for characters that have more than one other case when UCP
151        support is available.
152    
153        (a) The Unicode property table now has offsets into a new table of sets of
154            three or more characters that are case-equivalent. The MultiStage2.py
155            script that generates these tables (the pcre_ucd.c file) now scans
156            CaseFolding.txt instead of UnicodeData.txt for character case
157            information.
158    
159        (b) The code for adding characters or ranges of characters to a character
160            class has been abstracted into a generalized function that also handles
161            case-independence. In UTF-mode with UCP support, this uses the new data
162            to handle characters with more than one other case.
163    
164        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
165            whose other case is greater than 256 are now correctly matched
166            caselessly. Previously, the high codepoint matched the low one, but not
167            vice versa.
168    
169        (d) The processing of \h, \H, \v, and \ in character classes now makes use
170            of the new class addition function, using character lists defined as
171            macros alongside the case definitions of 20 above.
172    
173        (e) Caseless back references now work with characters that have more than
174            one other case.
175    
176        (f) General caseless matching of characters with more than one other case
177            is supported.
178    
179    22. Unicode character properties were updated from Unicode 6.2.0
180    
181    23. Improved CMake support under Windows. Patch by Daniel Richard G.
182    
183    24. Add support for 32-bit character strings, and UTF-32
184    
185    25. Major JIT compiler update (code refactoring and bugfixing).
186        Experimental Sparc 32 support is added.
187    
188    26. Applied a modified version of Daniel Richard G's patch to create
189        pcre.h.generic and config.h.generic by "make" instead of in the
190        PrepareRelease script.
191    
192    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
193        pcre_compile.c when checking for a zero character.
194    
195    28. Introducing a native interface for JIT. Through this interface, the compiled
196        machine code can be directly executed. The purpose of this interface is to
197        provide fast pattern matching, so several sanity checks are not performed.
198        However, feature tests are still performed. The new interface provides
199        1.4x speedup compared to the old one.
200    
201    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
202        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
203        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
204    
205    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
206        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
207        the "old" RFC 2279). Instead, it ended up passing a negative length to
208        pcre_exec().
209    
210    31. Add support for GCC's visibility feature to hide internal functions.
211    
212    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
213        "unknown -C option" after outputting 0 or 1.
214    
215    33. There is now support for generating a code coverage report for the test
216        suite in environments where gcc is the compiler and lcov is installed. This
217        is mainly for the benefit of the developers.
218    
219    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
220        unaddressable using valgrind annotations, allowing valgrind to detect
221        invalid memory accesses. This is mainly for the benefit of the developers.
222    
223    25. (*UTF) can now be used to start a pattern in any of the three libraries.
224    
225    26. Give configure error if --enable-cpp but no C++ compiler found.
226    
227    
228    Version 8.31 06-July-2012
229    -------------------------
230    
231  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
232    
233  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
234    
235  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
236      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
237      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
238    
239  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 242  Version 8.31
242      of more than one character:      of more than one character:
243    
244      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
245          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
246          references.          references.
247    
248      (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
249          subject.          subject.
250    
251      (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
252          characters at the end of the subject.          characters at the end of the subject.
253    
254      (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 257  Version 8.31
257      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
258          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.
259    
260  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
261      running pcretest, the text "(JIT)" added to the output whenever JIT is      running pcretest, the text "(JIT)" added to the output whenever JIT is
262      actually used to run the match.      actually used to run the match.
263    
264  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+[+]
265      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
266    
267  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 270  Version 8.31
270    
271  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
272      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
273    
274  11. Add PCRE_INFO_MAXLOOKBEHIND.  11. Add PCRE_INFO_MAXLOOKBEHIND.
275    
276  12. Applied a (slightly modified) user-supplied patch that improves performance  12. Applied a (slightly modified) user-supplied patch that improves performance
277      when the heap is used for recursion (compiled with --disable-stack-for-      when the heap is used for recursion (compiled with --disable-stack-for-
278      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
279      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
280      possible. This sometimes gives as much as 30% improvement.      possible. This sometimes gives as much as 30% improvement.
281    
282    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
283        call.
284    
285    14. As documented, (*COMMIT) is now confined to within a positive assertion.
286    
287    15. It is now possible to link pcretest with libedit as an alternative to
288        libreadline.
289    
290    16. (*COMMIT) control verb is now supported by the JIT compiler.
291    
292    17. The Unicode data tables have been updated to Unicode 6.1.0.
293    
294    18. Added --file-list option to pcregrep.
295    
296    19. Added binary file support to pcregrep, including the -a, --binary-files,
297        -I, and --text options.
298    
299    20. The madvise function is renamed for posix_madvise for QNX compatibility
300        reasons. Fixed by Giuseppe D'Angelo.
301    
302    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
303    
304    22. Changed the option for creating symbolic links for 16-bit man pages from
305        -s to -sf so that re-installing does not cause issues.
306    
307    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
308    
309    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
310        matches in certain environments (the workspace was not being correctly
311        retained). Also added to pcre_dfa_exec() a simple plausibility check on
312        some of the workspace data at the beginning of a restart.
313    
314    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
315        was not doing so when it should - probably a typo introduced by SVN 528
316        (change 8.10/14).
317    
318    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
319        \w+ when the character tables indicated that \x{c4} was a word character.
320        There were several related cases, all because the tests for doing a table
321        lookup were testing for characters less than 127 instead of 255.
322    
323    27. If a pattern contains capturing parentheses that are not used in a match,
324        their slots in the ovector are set to -1. For those that are higher than
325        any matched groups, this happens at the end of processing. In the case when
326        there were back references that the ovector was too small to contain
327        (causing temporary malloc'd memory to be used during matching), and the
328        highest capturing number was not used, memory off the end of the ovector
329        was incorrectly being set to -1. (It was using the size of the temporary
330        memory instead of the true size.)
331    
332    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
333        ovector size, it uses memory at the end of the block that it has got.
334    
335    29. Check for an overlong MARK name and give an error at compile time. The
336        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
337    
338    30. JIT compiler update.
339    
340    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
341        Rill for the patch.
342    
343    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
344    
345    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
346    
347    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
348        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
349        was enabled.
350    
351    35. Improve JIT code generation for greedy plus quantifier.
352    
353    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
354        1 to "aa" instead of to an empty string. The bug affected repeated groups
355        that could potentially match an empty string.
356    
357    37. Optimizing single character iterators in JIT.
358    
359    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
360        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
361        codepoints that are too big for the mode are faulted, and in a UTF mode,
362        disallowed codepoints are also faulted.
363    
364    39. If PCRE was compiled with UTF support, in three places in the DFA
365        matcher there was code that should only have been obeyed in UTF mode, but
366        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
367        processing when bytes with values greater than 127 were present. In 16-bit
368        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
369        both cases the values are those that cannot be the first data item in a UTF
370        character. The three items that might have provoked this were recursions,
371        possessively repeated groups, and atomic groups.
372    
373    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
374        and pcregrep, because some OS require shared objects to be explicitly
375        passed to ld, causing the link step to fail if they are not.
376    
377    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
378        mode, patterns that started with \h* or \R* might be incorrectly matched.
379    
380    
381  Version 8.30 04-February-2012  Version 8.30 04-February-2012

Legend:
Removed from v.933  
changed lines
  Added in v.1250

  ViewVC Help
Powered by ViewVC 1.1.5