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

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

  ViewVC Help
Powered by ViewVC 1.1.5