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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.691  
changed lines
  Added in v.979

  ViewVC Help
Powered by ViewVC 1.1.5