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

Diff of /code/trunk/ChangeLog

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

revision 719 by ph10, Fri Oct 7 11:41:05 2011 UTC revision 1035 by ph10, Mon Sep 10 16:23:12 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.20 23-Sep-2011  Version 8.32
5    ------------
6    
7    1.  Improved JIT compiler optimizations for first character search and single
8        character iterators.
9    
10    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
11        Patch by Daniel Richard G.
12    
13    3.  Single character iterator optimizations in the JIT compiler.
14    
15    4.  Improved JIT compiler optimizations for character ranges.
16    
17    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
18        Reported by Giuseppe D'Angelo.
19    
20    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
21        of a line, was being set incorrectly in cases where .* appeared inside
22        atomic brackets at the start of a pattern, or where there was a subsequent
23        *PRUNE or *SKIP.
24    
25    7.  Improved instruction cache flush for POWER/PowerPC.
26        Patch by Daniel Richard G.
27    
28    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
29        grep:
30    
31        (a) There is now no limit to the number of patterns to be matched.
32    
33        (b) An error is given if a pattern is too long.
34    
35        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
36            are now supported.
37    
38        (d) --exclude-from and --include-from (multiple use) have been added.
39    
40        (e) Exclusions and inclusions now apply to all files and directories, not
41            just to those obtained from scanning a directory recursively.
42    
43        (f) Multiple uses of -f and --file-list are now supported.
44    
45        (g) In a Windows environment, the default for -d has been changed from
46            "read" (the GNU grep default) to "skip", because otherwise the presence
47            of a directory in the file list provokes an error.
48    
49        (h) The documentation has been revised and clarified in places.
50    
51    9.  Improve the matching speed of capturing brackets.
52    
53    10. Changed the meaning of \X so that it now matches a Unicode extended
54        grapheme cluster.
55    
56    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
57        out POSIX threads when JIT support is configured.
58    
59    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
60    
61    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
62        structure could go wrong in environments where size_t is not the same size
63        as int.
64    
65    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
66        set.
67    
68    15. The EBCDIC support had decayed; later updates to the code had included
69        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
70        general tidy up of EBCDIC-related issues, and the documentation was also
71        not quite right. There is now a test that can be run on ASCII systems to
72        check some of the EBCDIC-related things (but is it not a full test).
73    
74    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
75        in a small tidy to the code.
76    
77    
78    
79    Version 8.31 06-July-2012
80    -------------------------
81    
82    1.  Fixing a wrong JIT test case and some compiler warnings.
83    
84    2.  Removed a bashism from the RunTest script.
85    
86    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
87        to unsigned type, result still unsigned" that was given by an MS compiler
88        on encountering the code "-sizeof(xxx)".
89    
90    4.  Partial matching support is added to the JIT compiler.
91    
92    5.  Fixed several bugs concerned with partial matching of items that consist
93        of more than one character:
94    
95        (a) /^(..)\1/ did not partially match "aba" because checking references was
96            done on an "all or nothing" basis. This also applied to repeated
97            references.
98    
99        (b) \R did not give a hard partial match if \r was found at the end of the
100            subject.
101    
102        (c) \X did not give a hard partial match after matching one or more
103            characters at the end of the subject.
104    
105        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
106            a partial match for the string "\r".
107    
108        (e) When newline was set to CRLF, the metacharacter "." did not recognize
109            a partial match for a CR character at the end of the subject string.
110    
111    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
112        running pcretest, the text "(JIT)" added to the output whenever JIT is
113        actually used to run the match.
114    
115    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
116        or /S+[+] with a digit between 1 and 7.
117    
118    8.  OP_NOT now supports any UTF character not just single-byte ones.
119    
120    9.  (*MARK) control verb is now supported by the JIT compiler.
121    
122    10. The command "./RunTest list" lists the available tests without actually
123        running any of them. (Because I keep forgetting what they all are.)
124    
125    11. Add PCRE_INFO_MAXLOOKBEHIND.
126    
127    12. Applied a (slightly modified) user-supplied patch that improves performance
128        when the heap is used for recursion (compiled with --disable-stack-for-
129        recursion). Instead of malloc and free for each heap frame each time a
130        logical recursion happens, frames are retained on a chain and re-used where
131        possible. This sometimes gives as much as 30% improvement.
132    
133    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
134        call.
135    
136    14. As documented, (*COMMIT) is now confined to within a positive assertion.
137    
138    15. It is now possible to link pcretest with libedit as an alternative to
139        libreadline.
140    
141    16. (*COMMIT) control verb is now supported by the JIT compiler.
142    
143    17. The Unicode data tables have been updated to Unicode 6.1.0.
144    
145    18. Added --file-list option to pcregrep.
146    
147    19. Added binary file support to pcregrep, including the -a, --binary-files,
148        -I, and --text options.
149    
150    20. The madvise function is renamed for posix_madvise for QNX compatibility
151        reasons. Fixed by Giuseppe D'Angelo.
152    
153    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
154    
155    22. Changed the option for creating symbolic links for 16-bit man pages from
156        -s to -sf so that re-installing does not cause issues.
157    
158    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
159    
160    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
161        matches in certain environments (the workspace was not being correctly
162        retained). Also added to pcre_dfa_exec() a simple plausibility check on
163        some of the workspace data at the beginning of a restart.
164    
165    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
166        was not doing so when it should - probably a typo introduced by SVN 528
167        (change 8.10/14).
168    
169    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
170        \w+ when the character tables indicated that \x{c4} was a word character.
171        There were several related cases, all because the tests for doing a table
172        lookup were testing for characters less than 127 instead of 255.
173    
174    27. If a pattern contains capturing parentheses that are not used in a match,
175        their slots in the ovector are set to -1. For those that are higher than
176        any matched groups, this happens at the end of processing. In the case when
177        there were back references that the ovector was too small to contain
178        (causing temporary malloc'd memory to be used during matching), and the
179        highest capturing number was not used, memory off the end of the ovector
180        was incorrectly being set to -1. (It was using the size of the temporary
181        memory instead of the true size.)
182    
183    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
184        ovector size, it uses memory at the end of the block that it has got.
185    
186    29. Check for an overlong MARK name and give an error at compile time. The
187        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
188    
189    30. JIT compiler update.
190    
191    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
192        Rill for the patch.
193    
194    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
195    
196    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
197    
198    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
199        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
200        was enabled.
201    
202    35. Improve JIT code generation for greedy plus quantifier.
203    
204    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
205        1 to "aa" instead of to an empty string. The bug affected repeated groups
206        that could potentially match an empty string.
207    
208    37. Optimizing single character iterators in JIT.
209    
210    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
211        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
212        codepoints that are too big for the mode are faulted, and in a UTF mode,
213        disallowed codepoints are also faulted.
214    
215    39. If PCRE was compiled with UTF support, in three places in the DFA
216        matcher there was code that should only have been obeyed in UTF mode, but
217        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
218        processing when bytes with values greater than 127 were present. In 16-bit
219        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
220        both cases the values are those that cannot be the first data item in a UTF
221        character. The three items that might have provoked this were recursions,
222        possessively repeated groups, and atomic groups.
223    
224    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
225        and pcregrep, because some OS require shared objects to be explicitly
226        passed to ld, causing the link step to fail if they are not.
227    
228    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
229        mode, patterns that started with \h* or \R* might be incorrectly matched.
230    
231    
232    Version 8.30 04-February-2012
233    -----------------------------
234    
235    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
236        name is defined in ctype.h.
237    
238    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
239        only in quite long subpatterns.
240    
241    3.  Removed the function pcre_info(), which has been obsolete and deprecated
242        since it was replaced by pcre_fullinfo() in February 2000.
243    
244    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
245        match a (*MARK), and the match failed at the start of the subject, a
246        reference to memory before the start of the subject could occur. This bug
247        was introduced by fix 17 of release 8.21.
248    
249    5.  A reference to an unset group with zero minimum repetition was giving
250        totally wrong answers (in non-JavaScript-compatibility mode). For example,
251        /(another)?(\1?)test/ matched against "hello world test". This bug was
252        introduced in release 8.13.
253    
254    6.  Add support for 16-bit character strings (a large amount of work involving
255        many changes and refactorings).
256    
257    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
258        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
259        from a file.
260    
261    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
262        rounding is not applied in this particular case).
263    
264    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
265        if they appear, or are escaped, in patterns.
266    
267    10. Get rid of a number of -Wunused-but-set-variable warnings.
268    
269    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
270        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
271        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
272        also returns the mark "x". This bug applied to capturing parentheses,
273        non-capturing parentheses, and atomic parentheses. It also applied to some
274        assertions.
275    
276    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
277        information out of configure.ac instead of relying on pcre.h.generic, which
278        is not stored in the repository.
279    
280    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
281        -lreadline.
282    
283    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
284    
285    15. Applied Graycode's patch to put the top-level frame on the stack rather
286        than the heap when not using the stack for recursion. This gives a
287        performance improvement in many cases when recursion is not deep.
288    
289    16. Experimental code added to "pcretest -C" to output the stack frame size.
290    
291    
292    Version 8.21 12-Dec-2011
293    ------------------------
294    
295    1.  Updating the JIT compiler.
296    
297    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
298        are added as well.
299    
300    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
301        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
302        calling _pcre_jit_exec. Some extra comments are added.
303    
304    4.  (*MARK) settings inside atomic groups that do not contain any capturing
305        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
306        was introduced by change 18 for 8.20.
307    
308    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
309        ECMA-262 standard.
310    
311    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
312        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
313        This bug was probably introduced by change 9 of 8.13.
314    
315    7.  While fixing 6 above, I noticed that a number of other items were being
316        incorrectly rejected as "not fixed length". This arose partly because newer
317        opcodes had not been added to the fixed-length checking code. I have (a)
318        corrected the bug and added tests for these items, and (b) arranged for an
319        error to occur if an unknown opcode is encountered while checking for fixed
320        length instead of just assuming "not fixed length". The items that were
321        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
322        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
323        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
324    
325    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
326        being incorrectly compiled and would have given unpredicatble results.
327    
328    9.  A possessively repeated subpattern with minimum repeat count greater than
329        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
330        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
331        the first (A) could occur when it should not.
332    
333    10. Add a cast and remove a redundant test from the code.
334    
335    11. JIT should use pcre_malloc/pcre_free for allocation.
336    
337    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
338        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
339        is anything other than /usr, -L is still shown).
340    
341    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
342    
343    14. Perl does not support \N without a following name in a [] class; PCRE now
344        also gives an error.
345    
346    15. If a forward reference was repeated with an upper limit of around 2000,
347        it caused the error "internal error: overran compiling workspace". The
348        maximum number of forward references (including repeats) was limited by the
349        internal workspace, and dependent on the LINK_SIZE. The code has been
350        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
351        the default depends on LINK_SIZE. There is a new upper limit (for safety)
352        of around 200,000 forward references. While doing this, I also speeded up
353        the filling in of repeated forward references.
354    
355    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
356        incorrectly expecting the subject to contain another "a" after the start.
357    
358    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
359        in the match, the SKIP should be ignored. This was not happening; instead
360        the SKIP was being treated as NOMATCH. For patterns such as
361        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
362        tested.
363    
364    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
365        now much more compatible with Perl, in particular in cases where the result
366        is a non-match for a non-anchored pattern. For example, if
367        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
368        "m", where previously it did not return a name. A side effect of this
369        change is that for partial matches, the last encountered mark name is
370        returned, as for non matches. A number of tests that were previously not
371        Perl-compatible have been moved into the Perl-compatible test files. The
372        refactoring has had the pleasing side effect of removing one argument from
373        the match() function, thus reducing its stack requirements.
374    
375    19. If the /S+ option was used in pcretest to study a pattern using JIT,
376        subsequent uses of /S (without +) incorrectly behaved like /S+.
377    
378    21. Retrieve executable code size support for the JIT compiler and fixing
379        some warnings.
380    
381    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
382        not work when the shorter character appeared right at the end of the
383        subject string.
384    
385    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
386        systems.
387    
388    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
389        output it when the /M option is used in pcretest.
390    
391    25. The CheckMan script was not being included in the distribution. Also, added
392        an explicit "perl" to run Perl scripts from the PrepareRelease script
393        because this is reportedly needed in Windows.
394    
395    26. If study data was being save in a file and studying had not found a set of
396        "starts with" bytes for the pattern, the data written to the file (though
397        never used) was taken from uninitialized memory and so caused valgrind to
398        complain.
399    
400    27. Updated RunTest.bat as provided by Sheri Pierce.
401    
402    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
403    
404    29. Computation of memory usage for the table of capturing group names was
405        giving an unnecessarily large value.
406    
407    
408    Version 8.20 21-Oct-2011
409  ------------------------  ------------------------
410    
411  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
# Line 65  Version 8.20 23-Sep-2011 Line 469  Version 8.20 23-Sep-2011
469      pattern contains any instances of (*THEN). If it does not, the old      pattern contains any instances of (*THEN). If it does not, the old
470      optimizations are restored. It would be nice to do this on a per-group      optimizations are restored. It would be nice to do this on a per-group
471      basis, but at the moment that is not feasible.      basis, but at the moment that is not feasible.
472    
473  12. In some environments, the output of pcretest -C is CRLF terminated. This  12. In some environments, the output of pcretest -C is CRLF terminated. This
474      broke RunTest's code that checks for the link size. A single white space      broke RunTest's code that checks for the link size. A single white space
475      after the value is now allowed for.      character after the value is now allowed for.
476    
477  13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".  13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
478      For "fr", it uses the Windows-specific input and output files.      For "fr", it uses the Windows-specific input and output files.
479    
480  14. If (*THEN) appeared in a group that was called recursively or as a  14. If (*THEN) appeared in a group that was called recursively or as a
481      subroutine, it did not work as intended. [But see next item.]      subroutine, it did not work as intended. [But see next item.]
482    
483  15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex  15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
484      pattern fragments (but not containing any | characters). If A and B are      pattern fragments (but not containing any | characters). If A and B are
485      matched, but there is a failure in C so that it backtracks to (*THEN), PCRE      matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
486      was behaving differently to Perl. PCRE backtracked into A, but Perl goes to      was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
487      D. In other words, Perl considers parentheses that do not contain any |      D. In other words, Perl considers parentheses that do not contain any |
488      characters to be part of a surrounding alternative, whereas PCRE was      characters to be part of a surrounding alternative, whereas PCRE was
489      treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles      treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
490      differently. PCRE now behaves in the same way as Perl, except in the case      differently. PCRE now behaves in the same way as Perl, except in the case
491      of subroutine/recursion calls such as (?1) which have in any case always      of subroutine/recursion calls such as (?1) which have in any case always
492      been different (but PCRE had them first :-).      been different (but PCRE had them first :-).
493    
494  16. Related to 15 above: Perl does not treat the | in a conditional group as  16. Related to 15 above: Perl does not treat the | in a conditional group as
495      creating alternatives. Such a group is treated in the same way as an      creating alternatives. Such a group is treated in the same way as an
496      ordinary group without any | characters when processing (*THEN). PCRE has      ordinary group without any | characters when processing (*THEN). PCRE has
497      been changed to match Perl's behaviour.      been changed to match Perl's behaviour.
498    
499    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
500        RunGrepTest script failed.
501    
502    18. Change 22 for version 13 caused atomic groups to use more stack. This is
503        inevitable for groups that contain captures, but it can lead to a lot of
504        stack use in large patterns. The old behaviour has been restored for atomic
505        groups that do not contain any capturing parentheses.
506    
507    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
508        suppress the check for a minimum subject length at run time. (If it was
509        given to pcre_exec() or pcre_dfa_exec() it did work.)
510    
511    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
512        fail to work when decoding hex characters in data strings in EBCDIC
513        environments.
514    
515    21. It appears that in at least one Mac OS environment, the isxdigit() function
516        is implemented as a macro that evaluates to its argument more than once,
517        contravening the C 90 Standard (I haven't checked a later standard). There
518        was an instance in pcretest which caused it to go wrong when processing
519        \x{...} escapes in subject strings. The has been rewritten to avoid using
520        things like p++ in the argument of isxdigit().
521    
522    
523  Version 8.13 16-Aug-2011  Version 8.13 16-Aug-2011
524  ------------------------  ------------------------

Legend:
Removed from v.719  
changed lines
  Added in v.1035

  ViewVC Help
Powered by ViewVC 1.1.5