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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.753  
changed lines
  Added in v.1211

  ViewVC Help
Powered by ViewVC 1.1.5