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

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

  ViewVC Help
Powered by ViewVC 1.1.5