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

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

  ViewVC Help
Powered by ViewVC 1.1.5