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

Diff of /code/trunk/ChangeLog

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

revision 760 by ph10, Tue Nov 22 11:23:43 2011 UTC revision 970 by zherczeg, Sun May 27 05:28:19 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. 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    
124    Version 8.30 04-February-2012
125    -----------------------------
126    
127    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
128        name is defined in ctype.h.
129    
130    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
131        only in quite long subpatterns.
132    
133    3.  Removed the function pcre_info(), which has been obsolete and deprecated
134        since it was replaced by pcre_fullinfo() in February 2000.
135    
136    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
137        match a (*MARK), and the match failed at the start of the subject, a
138        reference to memory before the start of the subject could occur. This bug
139        was introduced by fix 17 of release 8.21.
140    
141    5.  A reference to an unset group with zero minimum repetition was giving
142        totally wrong answers (in non-JavaScript-compatibility mode). For example,
143        /(another)?(\1?)test/ matched against "hello world test". This bug was
144        introduced in release 8.13.
145    
146    6.  Add support for 16-bit character strings (a large amount of work involving
147        many changes and refactorings).
148    
149    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
150        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
151        from a file.
152    
153    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
154        rounding is not applied in this particular case).
155    
156    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
157        if they appear, or are escaped, in patterns.
158    
159    10. Get rid of a number of -Wunused-but-set-variable warnings.
160    
161    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
162        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
163        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
164        also returns the mark "x". This bug applied to capturing parentheses,
165        non-capturing parentheses, and atomic parentheses. It also applied to some
166        assertions.
167    
168    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
169        information out of configure.ac instead of relying on pcre.h.generic, which
170        is not stored in the repository.
171    
172    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
173        -lreadline.
174    
175    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
176    
177    15. Applied Graycode's patch to put the top-level frame on the stack rather
178        than the heap when not using the stack for recursion. This gives a
179        performance improvement in many cases when recursion is not deep.
180    
181    16. Experimental code added to "pcretest -C" to output the stack frame size.
182    
183    
184    Version 8.21 12-Dec-2011
185    ------------------------
186    
187  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
188    
# Line 13  Version 8.21 Line 193  Version 8.21
193      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
194      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
195    
196  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
197      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
198      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
199    
# Line 22  Version 8.21 Line 202  Version 8.21
202    
203  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
204      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
205      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
206    
207  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
208      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
209      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)
210      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
211      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
212      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
213      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
214      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
215      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
216    
217  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
218      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
219    
220  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
221      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
222      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
223      the first (A) could occur when it should not.      the first (A) could occur when it should not.
224    
225  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
226    
227  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
228    
229  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
230      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
231      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
232    
233  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.
234    
235  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
236      also gives an error.      also gives an error.
237    
238  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,
239      it caused the error "internal error: overran compiling workspace". This      it caused the error "internal error: overran compiling workspace". The
240      is now checked, and causes "too many forward references" instead.      maximum number of forward references (including repeats) was limited by the
241        internal workspace, and dependent on the LINK_SIZE. The code has been
242        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
243        the default depends on LINK_SIZE. There is a new upper limit (for safety)
244        of around 200,000 forward references. While doing this, I also speeded up
245        the filling in of repeated forward references.
246    
247    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
248        incorrectly expecting the subject to contain another "a" after the start.
249    
250    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
251        in the match, the SKIP should be ignored. This was not happening; instead
252        the SKIP was being treated as NOMATCH. For patterns such as
253        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
254        tested.
255    
256    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
257        now much more compatible with Perl, in particular in cases where the result
258        is a non-match for a non-anchored pattern. For example, if
259        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
260        "m", where previously it did not return a name. A side effect of this
261        change is that for partial matches, the last encountered mark name is
262        returned, as for non matches. A number of tests that were previously not
263        Perl-compatible have been moved into the Perl-compatible test files. The
264        refactoring has had the pleasing side effect of removing one argument from
265        the match() function, thus reducing its stack requirements.
266    
267    19. If the /S+ option was used in pcretest to study a pattern using JIT,
268        subsequent uses of /S (without +) incorrectly behaved like /S+.
269    
270    21. Retrieve executable code size support for the JIT compiler and fixing
271        some warnings.
272    
273    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
274        not work when the shorter character appeared right at the end of the
275        subject string.
276    
277    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
278        systems.
279    
280    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
281        output it when the /M option is used in pcretest.
282    
283    25. The CheckMan script was not being included in the distribution. Also, added
284        an explicit "perl" to run Perl scripts from the PrepareRelease script
285        because this is reportedly needed in Windows.
286    
287    26. If study data was being save in a file and studying had not found a set of
288        "starts with" bytes for the pattern, the data written to the file (though
289        never used) was taken from uninitialized memory and so caused valgrind to
290        complain.
291    
292    27. Updated RunTest.bat as provided by Sheri Pierce.
293    
294    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
295    
296    29. Computation of memory usage for the table of capturing group names was
297        giving an unnecessarily large value.
298    
299    
300  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011

Legend:
Removed from v.760  
changed lines
  Added in v.970

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12