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 1345 by ph10, Tue Jul 2 17:52:28 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.31  Version 8.34 xx-xxxx-201x
5    --------------------------
7    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8        executable memory. Patch inspired by Carsten Klein.
10    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
11        this macro is never tested and has no effect, because the work to support
12        coverage involves only compiling and linking options and special targets in
13        the Makefile. The comment in config.h implied that defining the macro would
14        enable coverage support, which is totally false. There was also support for
15        setting this macro in the CMake files (my fault, I just copied it from
16        configure). SUPPORT_GCOV has now been removed.
18    3.  Make a small performance improvement in strlen16() and strlen32() in
19        pcretest.
22    Version 8.33 28-May-2013
23    --------------------------
25    1.  Added 'U' to some constants that are compared to unsigned integers, to
26        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
27        variables that are added to signed variables, to ensure the result is
28        signed and can be negated.
30    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
31        CMake config files.
33    3.  Revise the creation of config.h.generic so that all boolean macros are
34        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
35        overriding via -D on the command line possible.
37    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
38        to unsigned int is reported to make a quite noticeable speed difference in
39        a specific Windows environment. Testing on Linux did also appear to show
40        some benefit (and it is clearly not harmful). Also fixed the definition of
41        Xop which should be unsigned.
43    5.  Related to (4), changing the definition of the intermediate variable cc
44        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
45        improvements.
47    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
48        unnecessary spaces.
50    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
51        and later.
53    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
55    9.  Optimizing fast_forward_start_bits in JIT.
57    10. Adding support for callouts in JIT, and fixing some issues revealed
58        during this work. Namely:
60        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
62        (b) Minimum length was not checked before the matching is started.
64    11. The value of capture_last that is passed to callouts was incorrect in some
65        cases when there was a capture on one path that was subsequently abandoned
66        after a backtrack. Also, the capture_last value is now reset after a
67        recursion, since all captures are also reset in this case.
69    12. The interpreter no longer returns the "too many substrings" error in the
70        case when an overflowing capture is in a branch that is subsequently
71        abandoned after a backtrack.
73    13. In the pathological case when an offset vector of size 2 is used, pcretest
74        now prints out the matched string after a yield of 0 or 1.
76    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
77        Only supported by the JIT compiler at the moment.
79    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
81    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
82        offset of the starting point of the matching process, provided the offsets
83        vector is large enough.
85    17. The \A escape now records a lookbehind value of 1, though its execution
86        does not actually inspect the previous character. This is to ensure that,
87        in partial multi-segment matching, at least one character from the old
88        segment is retained when a new segment is processed. Otherwise, if there
89        are no lookbehinds in the pattern, \A might match incorrectly at the start
90        of a new segment.
92    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
94    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
95        gives some modest performance improvement in 8-bit mode.
97    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
98        be expressed in certain programming languages using Universal Character
99        Names.
101    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
102        which points out that "non characters" are not "characters that may not
103        appear in Unicode strings" but rather "characters that are reserved for
104        internal use and have only local meaning".
106    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
107        there was a conditional group that depended on an assertion, if the
108        assertion was false, the callout that immediately followed the alternation
109        in the condition was skipped when pcre_exec() was used for matching.
111    23. Allow an explicit callout to be inserted before an assertion that is the
112        condition for a conditional group, for compatibility with automatic
113        callouts, which always insert a callout at this point.
115    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
116        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
118    25. (*PRUNE) is now supported by the JIT compiler.
120    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
122    27. Fix the case where there are two or more SKIPs with arguments that may be
123        ignored.
125    28. (*SKIP) is now supported by the JIT compiler.
127    29. (*THEN) is now supported by the JIT compiler.
129    30. Update RunTest with additional test selector options.
131    31. The way PCRE handles backtracking verbs has been changed in two ways.
133        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
134        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
135        backtracking. In some cases this makes it more Perl-compatible, but Perl's
136        rather obscure rules do not always do the same thing.
138        (2) Previously, backtracking verbs were confined within assertions. This is
139        no longer the case for positive assertions, except for (*ACCEPT). Again,
140        this sometimes improves Perl compatibility, and sometimes does not.
142    32. A number of tests that were in test 2 because Perl did things differently
143        have been moved to test 1, because either Perl or PCRE has changed, and
144        these tests are now compatible.
146    32. Backtracking control verbs are now handled in the same way in JIT and
147        interpreter.
149    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
150        contained a forward subroutine reference caused a compile error.
152    34. Auto-detect and optimize limited repetitions in JIT.
154    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
155        blocking (*UTF) etc.
157    36. In the interpreter, maximizing pattern repetitions for characters and
158        character types now use tail recursion, which reduces stack usage.
160    37. The value of the max lookbehind was not correctly preserved if a compiled
161        and saved regex was reloaded on a host of different endianness.
163    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
164        of the compiled pattern block, expand the flags field from 16 to 32 bits
165        because it was almost full.
167    39. Try madvise first before posix_madvise.
169    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
170        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
171        original change locked out all matches of empty strings. This has been
172        changed so that one match of an empty string per line is recognized.
173        Subsequent searches on the same line (for colouring or for --only-matching,
174        for example) do not recognize empty strings.
176    41. Applied a user patch to fix a number of spelling mistakes in comments.
178    42. Data lines longer than 65536 caused pcretest to crash.
180    43. Clarified the data type for length and startoffset arguments for pcre_exec
181        and pcre_dfa_exec in the function-specific man pages, where they were
182        explicitly stated to be in bytes, never having been updated. I also added
183        some clarification to the pcreapi man page.
185    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
186        a segmentation fault.
189    Version 8.32 30-November-2012
190  -----------------------------  -----------------------------
192    1.  Improved JIT compiler optimizations for first character search and single
193        character iterators.
195    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
196        Patch by Daniel Richard G.
198    3.  Single character iterator optimizations in the JIT compiler.
200    4.  Improved JIT compiler optimizations for character ranges.
202    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
203        Reported by Giuseppe D'Angelo.
205    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
206        of a line, was being set incorrectly in cases where .* appeared inside
207        atomic brackets at the start of a pattern, or where there was a subsequent
208        *PRUNE or *SKIP.
210    7.  Improved instruction cache flush for POWER/PowerPC.
211        Patch by Daniel Richard G.
213    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
214        grep:
216        (a) There is now no limit to the number of patterns to be matched.
218        (b) An error is given if a pattern is too long.
220        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
221            are now supported.
223        (d) --exclude-from and --include-from (multiple use) have been added.
225        (e) Exclusions and inclusions now apply to all files and directories, not
226            just to those obtained from scanning a directory recursively.
228        (f) Multiple uses of -f and --file-list are now supported.
230        (g) In a Windows environment, the default for -d has been changed from
231            "read" (the GNU grep default) to "skip", because otherwise the presence
232            of a directory in the file list provokes an error.
234        (h) The documentation has been revised and clarified in places.
236    9.  Improve the matching speed of capturing brackets.
238    10. Changed the meaning of \X so that it now matches a Unicode extended
239        grapheme cluster.
241    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
242        out POSIX threads when JIT support is configured.
244    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
246    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
247        structure could go wrong in environments where size_t is not the same size
248        as int.
250    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
251        set.
253    15. The EBCDIC support had decayed; later updates to the code had included
254        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
255        general tidy up of EBCDIC-related issues, and the documentation was also
256        not quite right. There is now a test that can be run on ASCII systems to
257        check some of the EBCDIC-related things (but is it not a full test).
259    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
260        in a small tidy to the code.
262    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
264    18. If the --only-matching (-o) option in pcregrep is specified multiple
265        times, each one causes appropriate output. For example, -o1 -o2 outputs the
266        substrings matched by the 1st and 2nd capturing parentheses. A separating
267        string can be specified by --om-separator (default empty).
269    19. Improving the first n character searches.
271    20. Turn case lists for horizontal and vertical white space into macros so that
272        they are defined only once.
274    21. This set of changes together give more compatible Unicode case-folding
275        behaviour for characters that have more than one other case when UCP
276        support is available.
278        (a) The Unicode property table now has offsets into a new table of sets of
279            three or more characters that are case-equivalent. The MultiStage2.py
280            script that generates these tables (the pcre_ucd.c file) now scans
281            CaseFolding.txt instead of UnicodeData.txt for character case
282            information.
284        (b) The code for adding characters or ranges of characters to a character
285            class has been abstracted into a generalized function that also handles
286            case-independence. In UTF-mode with UCP support, this uses the new data
287            to handle characters with more than one other case.
289        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
290            whose other case is greater than 256 are now correctly matched
291            caselessly. Previously, the high codepoint matched the low one, but not
292            vice versa.
294        (d) The processing of \h, \H, \v, and \ in character classes now makes use
295            of the new class addition function, using character lists defined as
296            macros alongside the case definitions of 20 above.
298        (e) Caseless back references now work with characters that have more than
299            one other case.
301        (f) General caseless matching of characters with more than one other case
302            is supported.
304    22. Unicode character properties were updated from Unicode 6.2.0
306    23. Improved CMake support under Windows. Patch by Daniel Richard G.
308    24. Add support for 32-bit character strings, and UTF-32
310    25. Major JIT compiler update (code refactoring and bugfixing).
311        Experimental Sparc 32 support is added.
313    26. Applied a modified version of Daniel Richard G's patch to create
314        pcre.h.generic and config.h.generic by "make" instead of in the
315        PrepareRelease script.
317    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
318        pcre_compile.c when checking for a zero character.
320    28. Introducing a native interface for JIT. Through this interface, the compiled
321        machine code can be directly executed. The purpose of this interface is to
322        provide fast pattern matching, so several sanity checks are not performed.
323        However, feature tests are still performed. The new interface provides
324        1.4x speedup compared to the old one.
326    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
327        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
328        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
330    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
331        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
332        the "old" RFC 2279). Instead, it ended up passing a negative length to
333        pcre_exec().
335    31. Add support for GCC's visibility feature to hide internal functions.
337    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
338        "unknown -C option" after outputting 0 or 1.
340    33. There is now support for generating a code coverage report for the test
341        suite in environments where gcc is the compiler and lcov is installed. This
342        is mainly for the benefit of the developers.
344    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
345        unaddressable using valgrind annotations, allowing valgrind to detect
346        invalid memory accesses. This is mainly for the benefit of the developers.
348    25. (*UTF) can now be used to start a pattern in any of the three libraries.
350    26. Give configure error if --enable-cpp but no C++ compiler found.
353    Version 8.31 06-July-2012
354    -------------------------
356  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
358  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
360  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
361      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
362      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
364    4.  Partial matching support is added to the JIT compiler.
366    5.  Fixed several bugs concerned with partial matching of items that consist
367        of more than one character:
369        (a) /^(..)\1/ did not partially match "aba" because checking references was
370            done on an "all or nothing" basis. This also applied to repeated
371            references.
373        (b) \R did not give a hard partial match if \r was found at the end of the
374            subject.
376        (c) \X did not give a hard partial match after matching one or more
377            characters at the end of the subject.
379        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
380            a partial match for the string "\r".
382        (e) When newline was set to CRLF, the metacharacter "." did not recognize
383            a partial match for a CR character at the end of the subject string.
385    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
386        running pcretest, the text "(JIT)" added to the output whenever JIT is
387        actually used to run the match.
389    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
390        or /S+[+] with a digit between 1 and 7.
392    8.  OP_NOT now supports any UTF character not just single-byte ones.
394    9.  (*MARK) control verb is now supported by the JIT compiler.
396    10. The command "./RunTest list" lists the available tests without actually
397        running any of them. (Because I keep forgetting what they all are.)
401    12. Applied a (slightly modified) user-supplied patch that improves performance
402        when the heap is used for recursion (compiled with --disable-stack-for-
403        recursion). Instead of malloc and free for each heap frame each time a
404        logical recursion happens, frames are retained on a chain and re-used where
405        possible. This sometimes gives as much as 30% improvement.
407    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
408        call.
410    14. As documented, (*COMMIT) is now confined to within a positive assertion.
412    15. It is now possible to link pcretest with libedit as an alternative to
413        libreadline.
415    16. (*COMMIT) control verb is now supported by the JIT compiler.
417    17. The Unicode data tables have been updated to Unicode 6.1.0.
419    18. Added --file-list option to pcregrep.
421    19. Added binary file support to pcregrep, including the -a, --binary-files,
422        -I, and --text options.
424    20. The madvise function is renamed for posix_madvise for QNX compatibility
425        reasons. Fixed by Giuseppe D'Angelo.
427    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
429    22. Changed the option for creating symbolic links for 16-bit man pages from
430        -s to -sf so that re-installing does not cause issues.
432    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
434    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
435        matches in certain environments (the workspace was not being correctly
436        retained). Also added to pcre_dfa_exec() a simple plausibility check on
437        some of the workspace data at the beginning of a restart.
439    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
440        was not doing so when it should - probably a typo introduced by SVN 528
441        (change 8.10/14).
443    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
444        \w+ when the character tables indicated that \x{c4} was a word character.
445        There were several related cases, all because the tests for doing a table
446        lookup were testing for characters less than 127 instead of 255.
448    27. If a pattern contains capturing parentheses that are not used in a match,
449        their slots in the ovector are set to -1. For those that are higher than
450        any matched groups, this happens at the end of processing. In the case when
451        there were back references that the ovector was too small to contain
452        (causing temporary malloc'd memory to be used during matching), and the
453        highest capturing number was not used, memory off the end of the ovector
454        was incorrectly being set to -1. (It was using the size of the temporary
455        memory instead of the true size.)
457    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
458        ovector size, it uses memory at the end of the block that it has got.
460    29. Check for an overlong MARK name and give an error at compile time. The
461        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
463    30. JIT compiler update.
465    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
466        Rill for the patch.
468    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
470    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
472    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
473        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
474        was enabled.
476    35. Improve JIT code generation for greedy plus quantifier.
478    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
479        1 to "aa" instead of to an empty string. The bug affected repeated groups
480        that could potentially match an empty string.
482    37. Optimizing single character iterators in JIT.
484    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
485        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
486        codepoints that are too big for the mode are faulted, and in a UTF mode,
487        disallowed codepoints are also faulted.
489    39. If PCRE was compiled with UTF support, in three places in the DFA
490        matcher there was code that should only have been obeyed in UTF mode, but
491        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
492        processing when bytes with values greater than 127 were present. In 16-bit
493        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
494        both cases the values are those that cannot be the first data item in a UTF
495        character. The three items that might have provoked this were recursions,
496        possessively repeated groups, and atomic groups.
498    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
499        and pcregrep, because some OS require shared objects to be explicitly
500        passed to ld, causing the link step to fail if they are not.
502    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
503        mode, patterns that started with \h* or \R* might be incorrectly matched.
506  Version 8.30 04-February-2012  Version 8.30 04-February-2012
507  -----------------------------  -----------------------------
# Line 1203  Version 7.9 11-Apr-09 Line 1693  Version 7.9 11-Apr-09
1693  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
1694      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
1695      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1696      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1697        8.33.]
1699  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
1700      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1446  Version 7.7 07-May-08 Line 1937  Version 7.7 07-May-08
1937      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
1938      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
1939      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
1940      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
1941      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
1942      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.913  
changed lines
  Added in v.1345

  ViewVC Help
Powered by ViewVC 1.1.5