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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.913  
changed lines
  Added in v.1324

  ViewVC Help
Powered by ViewVC 1.1.5