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 922 by ph10, Mon Feb 20 18:44:42 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  Version 8.31
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.  When matching is performed using JIT-compiled code, the flag bit
37        PCRE_EXTRA_USED_JIT is set in the pcre_extra block and can be tested by the
38        caller. This bit is checked by pcretest if JIT is requested by /S++ or -s++
39        (instead of just /S+ or -s+) and the text "(JIT)" added to the output if
40        the bit is set.
43    Version 8.30 04-February-2012
44    -----------------------------
46    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
47        name is defined in ctype.h.
49    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
50        only in quite long subpatterns.
52    3.  Removed the function pcre_info(), which has been obsolete and deprecated
53        since it was replaced by pcre_fullinfo() in February 2000.
55    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
56        match a (*MARK), and the match failed at the start of the subject, a
57        reference to memory before the start of the subject could occur. This bug
58        was introduced by fix 17 of release 8.21.
60    5.  A reference to an unset group with zero minimum repetition was giving
61        totally wrong answers (in non-JavaScript-compatibility mode). For example,
62        /(another)?(\1?)test/ matched against "hello world test". This bug was
63        introduced in release 8.13.
65    6.  Add support for 16-bit character strings (a large amount of work involving
66        many changes and refactorings).
68    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
69        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
70        from a file.
72    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
73        rounding is not applied in this particular case).
75    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
76        if they appear, or are escaped, in patterns.
78    10. Get rid of a number of -Wunused-but-set-variable warnings.
80    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
81        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
82        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
83        also returns the mark "x". This bug applied to capturing parentheses,
84        non-capturing parentheses, and atomic parentheses. It also applied to some
85        assertions.
87    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
88        information out of configure.ac instead of relying on pcre.h.generic, which
89        is not stored in the repository.
91    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
92        -lreadline.
94    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
96    15. Applied Graycode's patch to put the top-level frame on the stack rather
97        than the heap when not using the stack for recursion. This gives a
98        performance improvement in many cases when recursion is not deep.
100    16. Experimental code added to "pcretest -C" to output the stack frame size.
103    Version 8.21 12-Dec-2011
104    ------------------------
106    1.  Updating the JIT compiler.
108    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
109        are added as well.
111    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
112        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
113        calling _pcre_jit_exec. Some extra comments are added.
115    4.  (*MARK) settings inside atomic groups that do not contain any capturing
116        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
117        was introduced by change 18 for 8.20.
119    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
120        ECMA-262 standard.
122    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
123        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
124        This bug was probably introduced by change 9 of 8.13.
126    7.  While fixing 6 above, I noticed that a number of other items were being
127        incorrectly rejected as "not fixed length". This arose partly because newer
128        opcodes had not been added to the fixed-length checking code. I have (a)
129        corrected the bug and added tests for these items, and (b) arranged for an
130        error to occur if an unknown opcode is encountered while checking for fixed
131        length instead of just assuming "not fixed length". The items that were
132        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
133        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
134        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
136    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
137        being incorrectly compiled and would have given unpredicatble results.
139    9.  A possessively repeated subpattern with minimum repeat count greater than
140        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
141        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
142        the first (A) could occur when it should not.
144    10. Add a cast and remove a redundant test from the code.
146    11. JIT should use pcre_malloc/pcre_free for allocation.
148    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
149        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
150        is anything other than /usr, -L is still shown).
152    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
154    14. Perl does not support \N without a following name in a [] class; PCRE now
155        also gives an error.
157    15. If a forward reference was repeated with an upper limit of around 2000,
158        it caused the error "internal error: overran compiling workspace". The
159        maximum number of forward references (including repeats) was limited by the
160        internal workspace, and dependent on the LINK_SIZE. The code has been
161        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
162        the default depends on LINK_SIZE. There is a new upper limit (for safety)
163        of around 200,000 forward references. While doing this, I also speeded up
164        the filling in of repeated forward references.
166    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
167        incorrectly expecting the subject to contain another "a" after the start.
169    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
170        in the match, the SKIP should be ignored. This was not happening; instead
171        the SKIP was being treated as NOMATCH. For patterns such as
172        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
173        tested.
175    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
176        now much more compatible with Perl, in particular in cases where the result
177        is a non-match for a non-anchored pattern. For example, if
178        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
179        "m", where previously it did not return a name. A side effect of this
180        change is that for partial matches, the last encountered mark name is
181        returned, as for non matches. A number of tests that were previously not
182        Perl-compatible have been moved into the Perl-compatible test files. The
183        refactoring has had the pleasing side effect of removing one argument from
184        the match() function, thus reducing its stack requirements.
186    19. If the /S+ option was used in pcretest to study a pattern using JIT,
187        subsequent uses of /S (without +) incorrectly behaved like /S+.
189    21. Retrieve executable code size support for the JIT compiler and fixing
190        some warnings.
192    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
193        not work when the shorter character appeared right at the end of the
194        subject string.
196    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
197        systems.
199    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
200        output it when the /M option is used in pcretest.
202    25. The CheckMan script was not being included in the distribution. Also, added
203        an explicit "perl" to run Perl scripts from the PrepareRelease script
204        because this is reportedly needed in Windows.
206    26. If study data was being save in a file and studying had not found a set of
207        "starts with" bytes for the pattern, the data written to the file (though
208        never used) was taken from uninitialized memory and so caused valgrind to
209        complain.
211    27. Updated RunTest.bat as provided by Sheri Pierce.
213    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
215    29. Computation of memory usage for the table of capturing group names was
216        giving an unnecessarily large value.
219    Version 8.20 21-Oct-2011
220    ------------------------
222    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
223        a POSIX class. After further experiments with Perl, which convinced me that
224        Perl has bugs and confusions, a closing square bracket is no longer allowed
225        in a POSIX name. This bug also affected patterns with classes that started
226        with full stops.
228    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
229        captured substring, but while checking the failing first alternative,
230        substring 1 is temporarily captured. If the output vector supplied to
231        pcre_exec() was not big enough for this capture, the yield of the function
232        was still zero ("insufficient space for captured substrings"). This cannot
233        be totally fixed without adding another stack variable, which seems a lot
234        of expense for a edge case. However, I have improved the situation in cases
235        such as /(a)(b)x|abc/ matched against "abc", where the return code
236        indicates that fewer than the maximum number of slots in the ovector have
237        been set.
239    3.  Related to (2) above: when there are more back references in a pattern than
240        slots in the output vector, pcre_exec() uses temporary memory during
241        matching, and copies in the captures as far as possible afterwards. It was
242        using the entire output vector, but this conflicts with the specification
243        that only 2/3 is used for passing back captured substrings. Now it uses
244        only the first 2/3, for compatibility. This is, of course, another edge
245        case.
247    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
248        main code base, and can be used by building with --enable-jit. When this is
249        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
250        runtime --no-jit option is given.
252    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
253        ovector, the return from the function was zero, implying that there were
254        other matches that did not fit. The correct "exactly full" value is now
255        returned.
257    6.  If a subpattern that was called recursively or as a subroutine contained
258        (*PRUNE) or any other control that caused it to give a non-standard return,
259        invalid errors such as "Error -26 (nested recursion at the same subject
260        position)" or even infinite loops could occur.
262    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
263        computing the minimum length on reaching *ACCEPT, and so ended up with the
264        wrong value of 1 rather than 0. Further investigation indicates that
265        computing a minimum subject length in the presence of *ACCEPT is difficult
266        (think back references, subroutine calls), and so I have changed the code
267        so that no minimum is registered for a pattern that contains *ACCEPT.
269    8.  If (*THEN) was present in the first (true) branch of a conditional group,
270        it was not handled as intended. [But see 16 below.]
272    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
273        Sheri Pierce.
275    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
276        the first byte in a match must be "a".
278    11. Change 17 for 8.13 increased the recursion depth for patterns like
279        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
280        pattern contains any instances of (*THEN). If it does not, the old
281        optimizations are restored. It would be nice to do this on a per-group
282        basis, but at the moment that is not feasible.
284    12. In some environments, the output of pcretest -C is CRLF terminated. This
285        broke RunTest's code that checks for the link size. A single white space
286        character after the value is now allowed for.
288    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
289        For "fr", it uses the Windows-specific input and output files.
291    14. If (*THEN) appeared in a group that was called recursively or as a
292        subroutine, it did not work as intended. [But see next item.]
294    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
295        pattern fragments (but not containing any | characters). If A and B are
296        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
297        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
298        D. In other words, Perl considers parentheses that do not contain any |
299        characters to be part of a surrounding alternative, whereas PCRE was
300        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
301        differently. PCRE now behaves in the same way as Perl, except in the case
302        of subroutine/recursion calls such as (?1) which have in any case always
303        been different (but PCRE had them first :-).
305    16. Related to 15 above: Perl does not treat the | in a conditional group as
306        creating alternatives. Such a group is treated in the same way as an
307        ordinary group without any | characters when processing (*THEN). PCRE has
308        been changed to match Perl's behaviour.
310    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
311        RunGrepTest script failed.
313    18. Change 22 for version 13 caused atomic groups to use more stack. This is
314        inevitable for groups that contain captures, but it can lead to a lot of
315        stack use in large patterns. The old behaviour has been restored for atomic
316        groups that do not contain any capturing parentheses.
318    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
319        suppress the check for a minimum subject length at run time. (If it was
320        given to pcre_exec() or pcre_dfa_exec() it did work.)
322    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
323        fail to work when decoding hex characters in data strings in EBCDIC
324        environments.
326    21. It appears that in at least one Mac OS environment, the isxdigit() function
327        is implemented as a macro that evaluates to its argument more than once,
328        contravening the C 90 Standard (I haven't checked a later standard). There
329        was an instance in pcretest which caused it to go wrong when processing
330        \x{...} escapes in subject strings. The has been rewritten to avoid using
331        things like p++ in the argument of isxdigit().
334    Version 8.13 16-Aug-2011
335  ------------------------  ------------------------
337  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 428  Version 8.13 02-Aug-2011
428      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
429      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
430      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
431      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
433  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
434      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 519  Version 8.13 02-Aug-2011
519      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
520      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
521      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
522      more like Perl.      more like Perl. (But see 8.20/1 above.)
524  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
525      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 554  Version 8.13 02-Aug-2011
554      (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
555          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
557      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
558          PCRE is built.          PCRE is built.
560      (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 576  Version 8.13 02-Aug-2011
576      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
577      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
579    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
580        starting byte set, because \b was not being ignored.
583  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
584  ------------------------  ------------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5