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

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

  ViewVC Help
Powered by ViewVC 1.1.5