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

Legend:
Removed from v.654  
changed lines
  Added in v.957

  ViewVC Help
Powered by ViewVC 1.1.5