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

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

  ViewVC Help
Powered by ViewVC 1.1.5