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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.657  
changed lines
  Added in v.958

  ViewVC Help
Powered by ViewVC 1.1.5