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

Diff of /code/trunk/ChangeLog

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

revision 780 by ph10, Fri Dec 2 11:39:21 2011 UTC revision 1022 by ph10, Tue Aug 28 12:28:15 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.21  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    
62    
63    Version 8.31 06-July-2012
64    -------------------------
65    
66    1.  Fixing a wrong JIT test case and some compiler warnings.
67    
68    2.  Removed a bashism from the RunTest script.
69    
70    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
71        to unsigned type, result still unsigned" that was given by an MS compiler
72        on encountering the code "-sizeof(xxx)".
73    
74    4.  Partial matching support is added to the JIT compiler.
75    
76    5.  Fixed several bugs concerned with partial matching of items that consist
77        of more than one character:
78    
79        (a) /^(..)\1/ did not partially match "aba" because checking references was
80            done on an "all or nothing" basis. This also applied to repeated
81            references.
82    
83        (b) \R did not give a hard partial match if \r was found at the end of the
84            subject.
85    
86        (c) \X did not give a hard partial match after matching one or more
87            characters at the end of the subject.
88    
89        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
90            a partial match for the string "\r".
91    
92        (e) When newline was set to CRLF, the metacharacter "." did not recognize
93            a partial match for a CR character at the end of the subject string.
94    
95    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
96        running pcretest, the text "(JIT)" added to the output whenever JIT is
97        actually used to run the match.
98    
99    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
100        or /S+[+] with a digit between 1 and 7.
101    
102    8.  OP_NOT now supports any UTF character not just single-byte ones.
103    
104    9.  (*MARK) control verb is now supported by the JIT compiler.
105    
106    10. The command "./RunTest list" lists the available tests without actually
107        running any of them. (Because I keep forgetting what they all are.)
108    
109    11. Add PCRE_INFO_MAXLOOKBEHIND.
110    
111    12. Applied a (slightly modified) user-supplied patch that improves performance
112        when the heap is used for recursion (compiled with --disable-stack-for-
113        recursion). Instead of malloc and free for each heap frame each time a
114        logical recursion happens, frames are retained on a chain and re-used where
115        possible. This sometimes gives as much as 30% improvement.
116    
117    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
118        call.
119    
120    14. As documented, (*COMMIT) is now confined to within a positive assertion.
121    
122    15. It is now possible to link pcretest with libedit as an alternative to
123        libreadline.
124    
125    16. (*COMMIT) control verb is now supported by the JIT compiler.
126    
127    17. The Unicode data tables have been updated to Unicode 6.1.0.
128    
129    18. Added --file-list option to pcregrep.
130    
131    19. Added binary file support to pcregrep, including the -a, --binary-files,
132        -I, and --text options.
133    
134    20. The madvise function is renamed for posix_madvise for QNX compatibility
135        reasons. Fixed by Giuseppe D'Angelo.
136    
137    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
138    
139    22. Changed the option for creating symbolic links for 16-bit man pages from
140        -s to -sf so that re-installing does not cause issues.
141    
142    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
143    
144    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
145        matches in certain environments (the workspace was not being correctly
146        retained). Also added to pcre_dfa_exec() a simple plausibility check on
147        some of the workspace data at the beginning of a restart.
148    
149    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
150        was not doing so when it should - probably a typo introduced by SVN 528
151        (change 8.10/14).
152    
153    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
154        \w+ when the character tables indicated that \x{c4} was a word character.
155        There were several related cases, all because the tests for doing a table
156        lookup were testing for characters less than 127 instead of 255.
157    
158    27. If a pattern contains capturing parentheses that are not used in a match,
159        their slots in the ovector are set to -1. For those that are higher than
160        any matched groups, this happens at the end of processing. In the case when
161        there were back references that the ovector was too small to contain
162        (causing temporary malloc'd memory to be used during matching), and the
163        highest capturing number was not used, memory off the end of the ovector
164        was incorrectly being set to -1. (It was using the size of the temporary
165        memory instead of the true size.)
166    
167    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
168        ovector size, it uses memory at the end of the block that it has got.
169    
170    29. Check for an overlong MARK name and give an error at compile time. The
171        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
172    
173    30. JIT compiler update.
174    
175    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
176        Rill for the patch.
177    
178    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
179    
180    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
181    
182    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
183        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
184        was enabled.
185    
186    35. Improve JIT code generation for greedy plus quantifier.
187    
188    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
189        1 to "aa" instead of to an empty string. The bug affected repeated groups
190        that could potentially match an empty string.
191    
192    37. Optimizing single character iterators in JIT.
193    
194    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
195        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
196        codepoints that are too big for the mode are faulted, and in a UTF mode,
197        disallowed codepoints are also faulted.
198    
199    39. If PCRE was compiled with UTF support, in three places in the DFA
200        matcher there was code that should only have been obeyed in UTF mode, but
201        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
202        processing when bytes with values greater than 127 were present. In 16-bit
203        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
204        both cases the values are those that cannot be the first data item in a UTF
205        character. The three items that might have provoked this were recursions,
206        possessively repeated groups, and atomic groups.
207    
208    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
209        and pcregrep, because some OS require shared objects to be explicitly
210        passed to ld, causing the link step to fail if they are not.
211    
212    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
213        mode, patterns that started with \h* or \R* might be incorrectly matched.
214    
215    
216    Version 8.30 04-February-2012
217    -----------------------------
218    
219    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
220        name is defined in ctype.h.
221    
222    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
223        only in quite long subpatterns.
224    
225    3.  Removed the function pcre_info(), which has been obsolete and deprecated
226        since it was replaced by pcre_fullinfo() in February 2000.
227    
228    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
229        match a (*MARK), and the match failed at the start of the subject, a
230        reference to memory before the start of the subject could occur. This bug
231        was introduced by fix 17 of release 8.21.
232    
233    5.  A reference to an unset group with zero minimum repetition was giving
234        totally wrong answers (in non-JavaScript-compatibility mode). For example,
235        /(another)?(\1?)test/ matched against "hello world test". This bug was
236        introduced in release 8.13.
237    
238    6.  Add support for 16-bit character strings (a large amount of work involving
239        many changes and refactorings).
240    
241    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
242        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
243        from a file.
244    
245    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
246        rounding is not applied in this particular case).
247    
248    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
249        if they appear, or are escaped, in patterns.
250    
251    10. Get rid of a number of -Wunused-but-set-variable warnings.
252    
253    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
254        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
255        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
256        also returns the mark "x". This bug applied to capturing parentheses,
257        non-capturing parentheses, and atomic parentheses. It also applied to some
258        assertions.
259    
260    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
261        information out of configure.ac instead of relying on pcre.h.generic, which
262        is not stored in the repository.
263    
264    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
265        -lreadline.
266    
267    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
268    
269    15. Applied Graycode's patch to put the top-level frame on the stack rather
270        than the heap when not using the stack for recursion. This gives a
271        performance improvement in many cases when recursion is not deep.
272    
273    16. Experimental code added to "pcretest -C" to output the stack frame size.
274    
275    
276    Version 8.21 12-Dec-2011
277    ------------------------
278    
279  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
280    
281  2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases  2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
# Line 13  Version 8.21 Line 285  Version 8.21
285      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
286      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
287    
288  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
289      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
290      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
291    
# Line 22  Version 8.21 Line 294  Version 8.21
294    
295  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
296      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
297      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
298    
299  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
300      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
301      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)
302      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
303      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
304      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
305      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
306      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
307      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
308    
309  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
310      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
311    
312  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
313      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
314      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
315      the first (A) could occur when it should not.      the first (A) could occur when it should not.
316    
317  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
318    
319  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
320    
321  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
322      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
323      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
324    
325  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.
326    
327  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
328      also gives an error.      also gives an error.
329    
330  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,
331      it caused the error "internal error: overran compiling workspace". The      it caused the error "internal error: overran compiling workspace". The
332      maximum number of forward references (including repeats) was limited by the      maximum number of forward references (including repeats) was limited by the
333      internal workspace, and dependent on the LINK_SIZE. The code has been      internal workspace, and dependent on the LINK_SIZE. The code has been
334      rewritten so that the workspace expands (via pcre_malloc) if necessary, and      rewritten so that the workspace expands (via pcre_malloc) if necessary, and
335      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)
336      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
337      the filling in of repeated forward references.      the filling in of repeated forward references.
338    
339  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
340      incorrectly expecting the subject to contain another "a" after the start.      incorrectly expecting the subject to contain another "a" after the start.
341    
342  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier  17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
343      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
344      the SKIP was being treated as NOMATCH. For patterns such as      the SKIP was being treated as NOMATCH. For patterns such as
345      /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
346      tested.      tested.
347    
348  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
349      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
350      is a non-match for a non-anchored pattern. For example, if      is a non-match for a non-anchored pattern. For example, if
351      /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
352      "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
353      change is that for partial matches, the last encountered mark name is      change is that for partial matches, the last encountered mark name is
354      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
355      Perl-compatible have been moved into the Perl-compatible test files. The      Perl-compatible have been moved into the Perl-compatible test files. The
356      refactoring has had the pleasing side effect of removing one argument from      refactoring has had the pleasing side effect of removing one argument from
357      the match() function, thus reducing its stack requirements.      the match() function, thus reducing its stack requirements.
358    
359  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,
360      subsequent uses of /S (without +) incorrectly behaved like /S+.      subsequent uses of /S (without +) incorrectly behaved like /S+.
361    
362  21. Retrieve executable code size support for the JIT compiler and fixing  21. Retrieve executable code size support for the JIT compiler and fixing
363      some warnings.      some warnings.
364    
365  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
366      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
367      subject string.      subject string.
368    
369  23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit  23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
370      systems.      systems.
371    
372  24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also  24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
373      output it when the /M option is used in pcretest.      output it when the /M option is used in pcretest.
374    
375    25. The CheckMan script was not being included in the distribution. Also, added
376        an explicit "perl" to run Perl scripts from the PrepareRelease script
377        because this is reportedly needed in Windows.
378    
379    26. If study data was being save in a file and studying had not found a set of
380        "starts with" bytes for the pattern, the data written to the file (though
381        never used) was taken from uninitialized memory and so caused valgrind to
382        complain.
383    
384    27. Updated RunTest.bat as provided by Sheri Pierce.
385    
386    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
387    
388    29. Computation of memory usage for the table of capturing group names was
389        giving an unnecessarily large value.
390    
391    
392  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011

Legend:
Removed from v.780  
changed lines
  Added in v.1022

  ViewVC Help
Powered by ViewVC 1.1.5