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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.778  
changed lines
  Added in v.980

  ViewVC Help
Powered by ViewVC 1.1.5