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

Diff of /code/trunk/ChangeLog

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

revision 777 by zherczeg, Thu Dec 1 15:15:31 2011 UTC revision 934 by ph10, Sat Feb 25 12:30:36 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.21  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. (*COMMIT) is now correctly confined to within a recursive subpattern call.
59    
60    
61    Version 8.30 04-February-2012
62    -----------------------------
63    
64    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
65        name is defined in ctype.h.
66    
67    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
68        only in quite long subpatterns.
69    
70    3.  Removed the function pcre_info(), which has been obsolete and deprecated
71        since it was replaced by pcre_fullinfo() in February 2000.
72    
73    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
74        match a (*MARK), and the match failed at the start of the subject, a
75        reference to memory before the start of the subject could occur. This bug
76        was introduced by fix 17 of release 8.21.
77    
78    5.  A reference to an unset group with zero minimum repetition was giving
79        totally wrong answers (in non-JavaScript-compatibility mode). For example,
80        /(another)?(\1?)test/ matched against "hello world test". This bug was
81        introduced in release 8.13.
82    
83    6.  Add support for 16-bit character strings (a large amount of work involving
84        many changes and refactorings).
85    
86    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
87        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
88        from a file.
89    
90    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
91        rounding is not applied in this particular case).
92    
93    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
94        if they appear, or are escaped, in patterns.
95    
96    10. Get rid of a number of -Wunused-but-set-variable warnings.
97    
98    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
99        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
100        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
101        also returns the mark "x". This bug applied to capturing parentheses,
102        non-capturing parentheses, and atomic parentheses. It also applied to some
103        assertions.
104    
105    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
106        information out of configure.ac instead of relying on pcre.h.generic, which
107        is not stored in the repository.
108    
109    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
110        -lreadline.
111    
112    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
113    
114    15. Applied Graycode's patch to put the top-level frame on the stack rather
115        than the heap when not using the stack for recursion. This gives a
116        performance improvement in many cases when recursion is not deep.
117    
118    16. Experimental code added to "pcretest -C" to output the stack frame size.
119    
120    
121    Version 8.21 12-Dec-2011
122    ------------------------
123    
124  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
125    
# Line 13  Version 8.21 Line 130  Version 8.21
130      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
131      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
132    
133  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
134      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
135      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
136    
# Line 22  Version 8.21 Line 139  Version 8.21
139    
140  6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were  6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
141      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
142      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
143    
144  7.  While fixing 6 above, I noticed that a number of other items were being  7.  While fixing 6 above, I noticed that a number of other items were being
145      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
146      opcodes had not been added to the fixed-length checking code. I have (a)      opcodes had not been added to the fixed-length checking code. I have (a)
147      corrected the bug and added tests for these items, and (b) arranged for an      corrected the bug and added tests for these items, and (b) arranged for an
148      error to occur if an unknown opcode is encountered while checking for fixed      error to occur if an unknown opcode is encountered while checking for fixed
149      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
150      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
151      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
152      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
153    
154  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
155      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
156    
157  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
158      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
159      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
160      the first (A) could occur when it should not.      the first (A) could occur when it should not.
161    
162  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
163    
164  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
165    
166  12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems  12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
167      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
168      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
169    
170  13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.  13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
171    
172  14. Perl does not support \N without a following name in a [] class; PCRE now  14. Perl does not support \N without a following name in a [] class; PCRE now
173      also gives an error.      also gives an error.
174    
175  15. If a forward reference was repeated with an upper limit of around 2000,  15. If a forward reference was repeated with an upper limit of around 2000,
176      it caused the error "internal error: overran compiling workspace". The      it caused the error "internal error: overran compiling workspace". The
177      maximum number of forward references (including repeats) was limited by the      maximum number of forward references (including repeats) was limited by the
178      internal workspace, and dependent on the LINK_SIZE. The code has been      internal workspace, and dependent on the LINK_SIZE. The code has been
179      rewritten so that the workspace expands (via pcre_malloc) if necessary, and      rewritten so that the workspace expands (via pcre_malloc) if necessary, and
180      the default depends on LINK_SIZE. There is a new upper limit (for safety)      the default depends on LINK_SIZE. There is a new upper limit (for safety)
181      of around 200,000 forward references. While doing this, I also speeded up      of around 200,000 forward references. While doing this, I also speeded up
182      the filling in of repeated forward references.      the filling in of repeated forward references.
183    
184  16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was  16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
185      incorrectly expecting the subject to contain another "a" after the start.      incorrectly expecting the subject to contain another "a" after the start.
186    
187  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
188      in the match, the SKIP should be ignored. This was not happening; instead      in the match, the SKIP should be ignored. This was not happening; instead
189      the SKIP was being treated as NOMATCH. For patterns such as      the SKIP was being treated as NOMATCH. For patterns such as
190      /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never      /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
191      tested.      tested.
192    
193  18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is  18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
194      now much more compatible with Perl, in particular in cases where the result      now much more compatible with Perl, in particular in cases where the result
195      is a non-match for a non-anchored pattern. For example, if      is a non-match for a non-anchored pattern. For example, if
196      /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name      /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
197      "m", where previously it did not return a name. A side effect of this      "m", where previously it did not return a name. A side effect of this
198      change is that for partial matches, the last encountered mark name is      change is that for partial matches, the last encountered mark name is
199      returned, as for non matches. A number of tests that were previously not      returned, as for non matches. A number of tests that were previously not
200      Perl-compatible have been moved into the Perl-compatible test files. The      Perl-compatible have been moved into the Perl-compatible test files. The
201      refactoring has had the pleasing side effect of removing one argument from      refactoring has had the pleasing side effect of removing one argument from
202      the match() function, thus reducing its stack requirements.      the match() function, thus reducing its stack requirements.
203    
204  19. If the /S+ option was used in pcretest to study a pattern using JIT,  19. If the /S+ option was used in pcretest to study a pattern using JIT,
205      subsequent uses of /S (without +) incorrectly behaved like /S+.      subsequent uses of /S (without +) incorrectly behaved like /S+.
206    
207  21. Retrieve executable code size support for the JIT compiler and fixing  21. Retrieve executable code size support for the JIT compiler and fixing
208      some warnings.      some warnings.
209    
210    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
211        not work when the shorter character appeared right at the end of the
212        subject string.
213    
214    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
215        systems.
216    
217    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
218        output it when the /M option is used in pcretest.
219    
220    25. The CheckMan script was not being included in the distribution. Also, added
221        an explicit "perl" to run Perl scripts from the PrepareRelease script
222        because this is reportedly needed in Windows.
223    
224    26. If study data was being save in a file and studying had not found a set of
225        "starts with" bytes for the pattern, the data written to the file (though
226        never used) was taken from uninitialized memory and so caused valgrind to
227        complain.
228    
229    27. Updated RunTest.bat as provided by Sheri Pierce.
230    
231    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
232    
233    29. Computation of memory usage for the table of capturing group names was
234        giving an unnecessarily large value.
235    
236    
237  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
238  ------------------------  ------------------------

Legend:
Removed from v.777  
changed lines
  Added in v.934

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12