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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.742  
changed lines
  Added in v.1053

  ViewVC Help
Powered by ViewVC 1.1.5