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

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

  ViewVC Help
Powered by ViewVC 1.1.5