ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 654 by ph10, Tue Aug 2 11:00:40 2011 UTC revision 976 by ph10, Sat Jun 16 17:53:17 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  Version 8.31 02-June-2012
5    -------------------------
7    1.  Fixing a wrong JIT test case and some compiler warnings.
9    2.  Removed a bashism from the RunTest script.
11    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
12        to unsigned type, result still unsigned" that was given by an MS compiler
13        on encountering the code "-sizeof(xxx)".
15    4.  Partial matching support is added to the JIT compiler.
17    5.  Fixed several bugs concerned with partial matching of items that consist
18        of more than one character:
20        (a) /^(..)\1/ did not partially match "aba" because checking references was
21            done on an "all or nothing" basis. This also applied to repeated
22            references.
24        (b) \R did not give a hard partial match if \r was found at the end of the
25            subject.
27        (c) \X did not give a hard partial match after matching one or more
28            characters at the end of the subject.
30        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
31            a partial match for the string "\r".
33        (e) When newline was set to CRLF, the metacharacter "." did not recognize
34            a partial match for a CR character at the end of the subject string.
36    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
37        running pcretest, the text "(JIT)" added to the output whenever JIT is
38        actually used to run the match.
40    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
41        or /S+[+] with a digit between 1 and 7.
43    8.  OP_NOT now supports any UTF character not just single-byte ones.
45    9.  (*MARK) control verb is now supported by the JIT compiler.
47    10. The command "./RunTest list" lists the available tests without actually
48        running any of them. (Because I keep forgetting what they all are.)
52    12. Applied a (slightly modified) user-supplied patch that improves performance
53        when the heap is used for recursion (compiled with --disable-stack-for-
54        recursion). Instead of malloc and free for each heap frame each time a
55        logical recursion happens, frames are retained on a chain and re-used where
56        possible. This sometimes gives as much as 30% improvement.
58    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
59        call.
61    14. As documented, (*COMMIT) is now confined to within a positive assertion.
63    15. It is now possible to link pcretest with libedit as an alternative to
64        libreadline.
66    16. (*COMMIT) control verb is now supported by the JIT compiler.
68    17. The Unicode data tables have been updated to Unicode 6.1.0.
70    18. Added --file-list option to pcregrep.
72    19. Added binary file support to pcregrep, including the -a, --binary-files,
73        -I, and --text options.
75    20. The madvise function is renamed for posix_madvise for QNX compatibility
76        reasons. Fixed by Giuseppe D'Angelo.
78    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
80    22. Changed the option for creating symbolic links for 16-bit man pages from
81        -s to -sf so that re-installing does not cause issues.
83    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
85    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
86        matches in certain environments (the workspace was not being correctly
87        retained). Also added to pcre_dfa_exec() a simple plausibility check on
88        some of the workspace data at the beginning of a restart.
90    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
91        was not doing so when it should - probably a typo introduced by SVN 528
92        (change 8.10/14).
94    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
95        \w+ when the character tables indicated that \x{c4} was a word character.
96        There were several related cases, all because the tests for doing a table
97        lookup were testing for characters less than 127 instead of 255.
99    27. If a pattern contains capturing parentheses that are not used in a match,
100        their slots in the ovector are set to -1. For those that are higher than
101        any matched groups, this happens at the end of processing. In the case when
102        there were back references that the ovector was too small to contain
103        (causing temporary malloc'd memory to be used during matching), and the
104        highest capturing number was not used, memory off the end of the ovector
105        was incorrectly being set to -1. (It was using the size of the temporary
106        memory instead of the true size.)
108    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
109        ovector size, it uses memory at the end of the block that it has got.
111    29. Check for an overlong MARK name and give an error at compile time. The
112        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
114    30. JIT compiler update.
116    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
117        Rill for the patch.
119    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
121    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
123    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
124        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
125        was enabled.
127    35. Improve JIT code generation for greedy plus quantifier.
129    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
130        1 to "aa" instead of to an empty string. The bug affected repeated groups
131        that could potentially match an empty string.
134    Version 8.30 04-February-2012
135    -----------------------------
137    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
138        name is defined in ctype.h.
140    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
141        only in quite long subpatterns.
143    3.  Removed the function pcre_info(), which has been obsolete and deprecated
144        since it was replaced by pcre_fullinfo() in February 2000.
146    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
147        match a (*MARK), and the match failed at the start of the subject, a
148        reference to memory before the start of the subject could occur. This bug
149        was introduced by fix 17 of release 8.21.
151    5.  A reference to an unset group with zero minimum repetition was giving
152        totally wrong answers (in non-JavaScript-compatibility mode). For example,
153        /(another)?(\1?)test/ matched against "hello world test". This bug was
154        introduced in release 8.13.
156    6.  Add support for 16-bit character strings (a large amount of work involving
157        many changes and refactorings).
159    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
160        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
161        from a file.
163    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
164        rounding is not applied in this particular case).
166    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
167        if they appear, or are escaped, in patterns.
169    10. Get rid of a number of -Wunused-but-set-variable warnings.
171    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
172        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
173        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
174        also returns the mark "x". This bug applied to capturing parentheses,
175        non-capturing parentheses, and atomic parentheses. It also applied to some
176        assertions.
178    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
179        information out of configure.ac instead of relying on pcre.h.generic, which
180        is not stored in the repository.
182    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
183        -lreadline.
185    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
187    15. Applied Graycode's patch to put the top-level frame on the stack rather
188        than the heap when not using the stack for recursion. This gives a
189        performance improvement in many cases when recursion is not deep.
191    16. Experimental code added to "pcretest -C" to output the stack frame size.
194    Version 8.21 12-Dec-2011
195    ------------------------
197    1.  Updating the JIT compiler.
199    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
200        are added as well.
202    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
203        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
204        calling _pcre_jit_exec. Some extra comments are added.
206    4.  (*MARK) settings inside atomic groups that do not contain any capturing
207        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
208        was introduced by change 18 for 8.20.
210    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
211        ECMA-262 standard.
213    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
214        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
215        This bug was probably introduced by change 9 of 8.13.
217    7.  While fixing 6 above, I noticed that a number of other items were being
218        incorrectly rejected as "not fixed length". This arose partly because newer
219        opcodes had not been added to the fixed-length checking code. I have (a)
220        corrected the bug and added tests for these items, and (b) arranged for an
221        error to occur if an unknown opcode is encountered while checking for fixed
222        length instead of just assuming "not fixed length". The items that were
223        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
224        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
225        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
227    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
228        being incorrectly compiled and would have given unpredicatble results.
230    9.  A possessively repeated subpattern with minimum repeat count greater than
231        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
232        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
233        the first (A) could occur when it should not.
235    10. Add a cast and remove a redundant test from the code.
237    11. JIT should use pcre_malloc/pcre_free for allocation.
239    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
240        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
241        is anything other than /usr, -L is still shown).
243    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
245    14. Perl does not support \N without a following name in a [] class; PCRE now
246        also gives an error.
248    15. If a forward reference was repeated with an upper limit of around 2000,
249        it caused the error "internal error: overran compiling workspace". The
250        maximum number of forward references (including repeats) was limited by the
251        internal workspace, and dependent on the LINK_SIZE. The code has been
252        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
253        the default depends on LINK_SIZE. There is a new upper limit (for safety)
254        of around 200,000 forward references. While doing this, I also speeded up
255        the filling in of repeated forward references.
257    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
258        incorrectly expecting the subject to contain another "a" after the start.
260    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
261        in the match, the SKIP should be ignored. This was not happening; instead
262        the SKIP was being treated as NOMATCH. For patterns such as
263        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
264        tested.
266    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
267        now much more compatible with Perl, in particular in cases where the result
268        is a non-match for a non-anchored pattern. For example, if
269        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
270        "m", where previously it did not return a name. A side effect of this
271        change is that for partial matches, the last encountered mark name is
272        returned, as for non matches. A number of tests that were previously not
273        Perl-compatible have been moved into the Perl-compatible test files. The
274        refactoring has had the pleasing side effect of removing one argument from
275        the match() function, thus reducing its stack requirements.
277    19. If the /S+ option was used in pcretest to study a pattern using JIT,
278        subsequent uses of /S (without +) incorrectly behaved like /S+.
280    21. Retrieve executable code size support for the JIT compiler and fixing
281        some warnings.
283    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
284        not work when the shorter character appeared right at the end of the
285        subject string.
287    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
288        systems.
290    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
291        output it when the /M option is used in pcretest.
293    25. The CheckMan script was not being included in the distribution. Also, added
294        an explicit "perl" to run Perl scripts from the PrepareRelease script
295        because this is reportedly needed in Windows.
297    26. If study data was being save in a file and studying had not found a set of
298        "starts with" bytes for the pattern, the data written to the file (though
299        never used) was taken from uninitialized memory and so caused valgrind to
300        complain.
302    27. Updated RunTest.bat as provided by Sheri Pierce.
304    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
306    29. Computation of memory usage for the table of capturing group names was
307        giving an unnecessarily large value.
310    Version 8.20 21-Oct-2011
311    ------------------------
313    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
314        a POSIX class. After further experiments with Perl, which convinced me that
315        Perl has bugs and confusions, a closing square bracket is no longer allowed
316        in a POSIX name. This bug also affected patterns with classes that started
317        with full stops.
319    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
320        captured substring, but while checking the failing first alternative,
321        substring 1 is temporarily captured. If the output vector supplied to
322        pcre_exec() was not big enough for this capture, the yield of the function
323        was still zero ("insufficient space for captured substrings"). This cannot
324        be totally fixed without adding another stack variable, which seems a lot
325        of expense for a edge case. However, I have improved the situation in cases
326        such as /(a)(b)x|abc/ matched against "abc", where the return code
327        indicates that fewer than the maximum number of slots in the ovector have
328        been set.
330    3.  Related to (2) above: when there are more back references in a pattern than
331        slots in the output vector, pcre_exec() uses temporary memory during
332        matching, and copies in the captures as far as possible afterwards. It was
333        using the entire output vector, but this conflicts with the specification
334        that only 2/3 is used for passing back captured substrings. Now it uses
335        only the first 2/3, for compatibility. This is, of course, another edge
336        case.
338    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
339        main code base, and can be used by building with --enable-jit. When this is
340        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
341        runtime --no-jit option is given.
343    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
344        ovector, the return from the function was zero, implying that there were
345        other matches that did not fit. The correct "exactly full" value is now
346        returned.
348    6.  If a subpattern that was called recursively or as a subroutine contained
349        (*PRUNE) or any other control that caused it to give a non-standard return,
350        invalid errors such as "Error -26 (nested recursion at the same subject
351        position)" or even infinite loops could occur.
353    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
354        computing the minimum length on reaching *ACCEPT, and so ended up with the
355        wrong value of 1 rather than 0. Further investigation indicates that
356        computing a minimum subject length in the presence of *ACCEPT is difficult
357        (think back references, subroutine calls), and so I have changed the code
358        so that no minimum is registered for a pattern that contains *ACCEPT.
360    8.  If (*THEN) was present in the first (true) branch of a conditional group,
361        it was not handled as intended. [But see 16 below.]
363    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
364        Sheri Pierce.
366    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
367        the first byte in a match must be "a".
369    11. Change 17 for 8.13 increased the recursion depth for patterns like
370        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
371        pattern contains any instances of (*THEN). If it does not, the old
372        optimizations are restored. It would be nice to do this on a per-group
373        basis, but at the moment that is not feasible.
375    12. In some environments, the output of pcretest -C is CRLF terminated. This
376        broke RunTest's code that checks for the link size. A single white space
377        character after the value is now allowed for.
379    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
380        For "fr", it uses the Windows-specific input and output files.
382    14. If (*THEN) appeared in a group that was called recursively or as a
383        subroutine, it did not work as intended. [But see next item.]
385    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
386        pattern fragments (but not containing any | characters). If A and B are
387        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
388        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
389        D. In other words, Perl considers parentheses that do not contain any |
390        characters to be part of a surrounding alternative, whereas PCRE was
391        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
392        differently. PCRE now behaves in the same way as Perl, except in the case
393        of subroutine/recursion calls such as (?1) which have in any case always
394        been different (but PCRE had them first :-).
396    16. Related to 15 above: Perl does not treat the | in a conditional group as
397        creating alternatives. Such a group is treated in the same way as an
398        ordinary group without any | characters when processing (*THEN). PCRE has
399        been changed to match Perl's behaviour.
401    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
402        RunGrepTest script failed.
404    18. Change 22 for version 13 caused atomic groups to use more stack. This is
405        inevitable for groups that contain captures, but it can lead to a lot of
406        stack use in large patterns. The old behaviour has been restored for atomic
407        groups that do not contain any capturing parentheses.
409    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
410        suppress the check for a minimum subject length at run time. (If it was
411        given to pcre_exec() or pcre_dfa_exec() it did work.)
413    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
414        fail to work when decoding hex characters in data strings in EBCDIC
415        environments.
417    21. It appears that in at least one Mac OS environment, the isxdigit() function
418        is implemented as a macro that evaluates to its argument more than once,
419        contravening the C 90 Standard (I haven't checked a later standard). There
420        was an instance in pcretest which caused it to go wrong when processing
421        \x{...} escapes in subject strings. The has been rewritten to avoid using
422        things like p++ in the argument of isxdigit().
425    Version 8.13 16-Aug-2011
426  ------------------------  ------------------------
428  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 98  Version 8.13 02-Aug-2011 Line 519  Version 8.13 02-Aug-2011
519      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
520      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
521      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
522      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
524  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
525      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 610  Version 8.13 02-Aug-2011
610      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
611      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
612      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
613      more like Perl.      more like Perl. (But see 8.20/1 above.)
615  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
616      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 645  Version 8.13 02-Aug-2011
645      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
646          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
648      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
649          PCRE is built.          PCRE is built.
651      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 246  Version 8.13 02-Aug-2011 Line 667  Version 8.13 02-Aug-2011
667      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
668      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
670    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
671        starting byte set, because \b was not being ignored.
674  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
675  ------------------------  ------------------------

Removed from v.654  
changed lines
  Added in v.976

  ViewVC Help
Powered by ViewVC 1.1.5