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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.740  
changed lines
  Added in v.1238

  ViewVC Help
Powered by ViewVC 1.1.5