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

Diff of /code/trunk/ChangeLog

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

revision 836 by ph10, Wed Dec 28 17:16:11 2011 UTC revision 1234 by ph10, Sat Dec 8 16:35:42 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.30  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    
16    Version 8.32 30-November-2012
17    -----------------------------
18    
19    1.  Improved JIT compiler optimizations for first character search and single
20        character iterators.
21    
22    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
23        Patch by Daniel Richard G.
24    
25    3.  Single character iterator optimizations in the JIT compiler.
26    
27    4.  Improved JIT compiler optimizations for character ranges.
28    
29    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
30        Reported by Giuseppe D'Angelo.
31    
32    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
33        of a line, was being set incorrectly in cases where .* appeared inside
34        atomic brackets at the start of a pattern, or where there was a subsequent
35        *PRUNE or *SKIP.
36    
37    7.  Improved instruction cache flush for POWER/PowerPC.
38        Patch by Daniel Richard G.
39    
40    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
41        grep:
42    
43        (a) There is now no limit to the number of patterns to be matched.
44    
45        (b) An error is given if a pattern is too long.
46    
47        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
48            are now supported.
49    
50        (d) --exclude-from and --include-from (multiple use) have been added.
51    
52        (e) Exclusions and inclusions now apply to all files and directories, not
53            just to those obtained from scanning a directory recursively.
54    
55        (f) Multiple uses of -f and --file-list are now supported.
56    
57        (g) In a Windows environment, the default for -d has been changed from
58            "read" (the GNU grep default) to "skip", because otherwise the presence
59            of a directory in the file list provokes an error.
60    
61        (h) The documentation has been revised and clarified in places.
62    
63    9.  Improve the matching speed of capturing brackets.
64    
65    10. Changed the meaning of \X so that it now matches a Unicode extended
66        grapheme cluster.
67    
68    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
69        out POSIX threads when JIT support is configured.
70    
71    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
72    
73    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
74        structure could go wrong in environments where size_t is not the same size
75        as int.
76    
77    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
78        set.
79    
80    15. The EBCDIC support had decayed; later updates to the code had included
81        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
82        general tidy up of EBCDIC-related issues, and the documentation was also
83        not quite right. There is now a test that can be run on ASCII systems to
84        check some of the EBCDIC-related things (but is it not a full test).
85    
86    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
87        in a small tidy to the code.
88    
89    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
90    
91    18. If the --only-matching (-o) option in pcregrep is specified multiple
92        times, each one causes appropriate output. For example, -o1 -o2 outputs the
93        substrings matched by the 1st and 2nd capturing parentheses. A separating
94        string can be specified by --om-separator (default empty).
95    
96    19. Improving the first n character searches.
97    
98    20. Turn case lists for horizontal and vertical white space into macros so that
99        they are defined only once.
100    
101    21. This set of changes together give more compatible Unicode case-folding
102        behaviour for characters that have more than one other case when UCP
103        support is available.
104    
105        (a) The Unicode property table now has offsets into a new table of sets of
106            three or more characters that are case-equivalent. The MultiStage2.py
107            script that generates these tables (the pcre_ucd.c file) now scans
108            CaseFolding.txt instead of UnicodeData.txt for character case
109            information.
110    
111        (b) The code for adding characters or ranges of characters to a character
112            class has been abstracted into a generalized function that also handles
113            case-independence. In UTF-mode with UCP support, this uses the new data
114            to handle characters with more than one other case.
115    
116        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
117            whose other case is greater than 256 are now correctly matched
118            caselessly. Previously, the high codepoint matched the low one, but not
119            vice versa.
120    
121        (d) The processing of \h, \H, \v, and \ in character classes now makes use
122            of the new class addition function, using character lists defined as
123            macros alongside the case definitions of 20 above.
124    
125        (e) Caseless back references now work with characters that have more than
126            one other case.
127    
128        (f) General caseless matching of characters with more than one other case
129            is supported.
130    
131    22. Unicode character properties were updated from Unicode 6.2.0
132    
133    23. Improved CMake support under Windows. Patch by Daniel Richard G.
134    
135    24. Add support for 32-bit character strings, and UTF-32
136    
137    25. Major JIT compiler update (code refactoring and bugfixing).
138        Experimental Sparc 32 support is added.
139    
140    26. Applied a modified version of Daniel Richard G's patch to create
141        pcre.h.generic and config.h.generic by "make" instead of in the
142        PrepareRelease script.
143    
144    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
145        pcre_compile.c when checking for a zero character.
146    
147    28. Introducing a native interface for JIT. Through this interface, the compiled
148        machine code can be directly executed. The purpose of this interface is to
149        provide fast pattern matching, so several sanity checks are not performed.
150        However, feature tests are still performed. The new interface provides
151        1.4x speedup compared to the old one.
152    
153    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
154        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
155        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
156    
157    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
158        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
159        the "old" RFC 2279). Instead, it ended up passing a negative length to
160        pcre_exec().
161    
162    31. Add support for GCC's visibility feature to hide internal functions.
163    
164    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
165        "unknown -C option" after outputting 0 or 1.
166    
167    33. There is now support for generating a code coverage report for the test
168        suite in environments where gcc is the compiler and lcov is installed. This
169        is mainly for the benefit of the developers.
170    
171    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
172        unaddressable using valgrind annotations, allowing valgrind to detect
173        invalid memory accesses. This is mainly for the benefit of the developers.
174    
175    25. (*UTF) can now be used to start a pattern in any of the three libraries.
176    
177    26. Give configure error if --enable-cpp but no C++ compiler found.
178    
179    
180    Version 8.31 06-July-2012
181    -------------------------
182    
183    1.  Fixing a wrong JIT test case and some compiler warnings.
184    
185    2.  Removed a bashism from the RunTest script.
186    
187    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
188        to unsigned type, result still unsigned" that was given by an MS compiler
189        on encountering the code "-sizeof(xxx)".
190    
191    4.  Partial matching support is added to the JIT compiler.
192    
193    5.  Fixed several bugs concerned with partial matching of items that consist
194        of more than one character:
195    
196        (a) /^(..)\1/ did not partially match "aba" because checking references was
197            done on an "all or nothing" basis. This also applied to repeated
198            references.
199    
200        (b) \R did not give a hard partial match if \r was found at the end of the
201            subject.
202    
203        (c) \X did not give a hard partial match after matching one or more
204            characters at the end of the subject.
205    
206        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
207            a partial match for the string "\r".
208    
209        (e) When newline was set to CRLF, the metacharacter "." did not recognize
210            a partial match for a CR character at the end of the subject string.
211    
212    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
213        running pcretest, the text "(JIT)" added to the output whenever JIT is
214        actually used to run the match.
215    
216    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
217        or /S+[+] with a digit between 1 and 7.
218    
219    8.  OP_NOT now supports any UTF character not just single-byte ones.
220    
221    9.  (*MARK) control verb is now supported by the JIT compiler.
222    
223    10. The command "./RunTest list" lists the available tests without actually
224        running any of them. (Because I keep forgetting what they all are.)
225    
226    11. Add PCRE_INFO_MAXLOOKBEHIND.
227    
228    12. Applied a (slightly modified) user-supplied patch that improves performance
229        when the heap is used for recursion (compiled with --disable-stack-for-
230        recursion). Instead of malloc and free for each heap frame each time a
231        logical recursion happens, frames are retained on a chain and re-used where
232        possible. This sometimes gives as much as 30% improvement.
233    
234    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
235        call.
236    
237    14. As documented, (*COMMIT) is now confined to within a positive assertion.
238    
239    15. It is now possible to link pcretest with libedit as an alternative to
240        libreadline.
241    
242    16. (*COMMIT) control verb is now supported by the JIT compiler.
243    
244    17. The Unicode data tables have been updated to Unicode 6.1.0.
245    
246    18. Added --file-list option to pcregrep.
247    
248    19. Added binary file support to pcregrep, including the -a, --binary-files,
249        -I, and --text options.
250    
251    20. The madvise function is renamed for posix_madvise for QNX compatibility
252        reasons. Fixed by Giuseppe D'Angelo.
253    
254    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
255    
256    22. Changed the option for creating symbolic links for 16-bit man pages from
257        -s to -sf so that re-installing does not cause issues.
258    
259    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
260    
261    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
262        matches in certain environments (the workspace was not being correctly
263        retained). Also added to pcre_dfa_exec() a simple plausibility check on
264        some of the workspace data at the beginning of a restart.
265    
266    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
267        was not doing so when it should - probably a typo introduced by SVN 528
268        (change 8.10/14).
269    
270    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
271        \w+ when the character tables indicated that \x{c4} was a word character.
272        There were several related cases, all because the tests for doing a table
273        lookup were testing for characters less than 127 instead of 255.
274    
275    27. If a pattern contains capturing parentheses that are not used in a match,
276        their slots in the ovector are set to -1. For those that are higher than
277        any matched groups, this happens at the end of processing. In the case when
278        there were back references that the ovector was too small to contain
279        (causing temporary malloc'd memory to be used during matching), and the
280        highest capturing number was not used, memory off the end of the ovector
281        was incorrectly being set to -1. (It was using the size of the temporary
282        memory instead of the true size.)
283    
284    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
285        ovector size, it uses memory at the end of the block that it has got.
286    
287    29. Check for an overlong MARK name and give an error at compile time. The
288        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
289    
290    30. JIT compiler update.
291    
292    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
293        Rill for the patch.
294    
295    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
296    
297    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
298    
299    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
300        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
301        was enabled.
302    
303    35. Improve JIT code generation for greedy plus quantifier.
304    
305    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
306        1 to "aa" instead of to an empty string. The bug affected repeated groups
307        that could potentially match an empty string.
308    
309    37. Optimizing single character iterators in JIT.
310    
311    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
312        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
313        codepoints that are too big for the mode are faulted, and in a UTF mode,
314        disallowed codepoints are also faulted.
315    
316    39. If PCRE was compiled with UTF support, in three places in the DFA
317        matcher there was code that should only have been obeyed in UTF mode, but
318        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
319        processing when bytes with values greater than 127 were present. In 16-bit
320        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
321        both cases the values are those that cannot be the first data item in a UTF
322        character. The three items that might have provoked this were recursions,
323        possessively repeated groups, and atomic groups.
324    
325    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
326        and pcregrep, because some OS require shared objects to be explicitly
327        passed to ld, causing the link step to fail if they are not.
328    
329    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
330        mode, patterns that started with \h* or \R* might be incorrectly matched.
331    
332    
333    Version 8.30 04-February-2012
334    -----------------------------
335    
336  1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this  1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
337      name is defined in ctype.h.      name is defined in ctype.h.
338    
339  2.  Fixed a bug in the code for calculating the fixed length of lookbehind  2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
340      assertions.      only in quite long subpatterns.
341    
342  3.  Removed the function pcre_info(), which has been obsolete and deprecated  3.  Removed the function pcre_info(), which has been obsolete and deprecated
343      since it was replaced by pcre_fullinfo() in February 2000.      since it was replaced by pcre_fullinfo() in February 2000.
344    
345  4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not  4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
346      match a (*MARK), and the match failed at the start of the subject, a      match a (*MARK), and the match failed at the start of the subject, a
347      reference to memory before the start of the subject could occur. This bug      reference to memory before the start of the subject could occur. This bug
348      was introduced by fix 17 of release 8.21.      was introduced by fix 17 of release 8.21.
349    
350  5.  A reference to an unset group with zero minimum repetition was giving  5.  A reference to an unset group with zero minimum repetition was giving
351      totally wrong answers (in non-JavaScript-compatibility mode). For example,      totally wrong answers (in non-JavaScript-compatibility mode). For example,
352      /(another)?(\1?)test/ matched against "hello world test". This bug was      /(another)?(\1?)test/ matched against "hello world test". This bug was
353      introduced in release 8.13.      introduced in release 8.13.
354    
355  6.  Add support for 16-bit character strings (a large amount of work involving  6.  Add support for 16-bit character strings (a large amount of work involving
356      many changes and refactorings).      many changes and refactorings).
357    
358    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
359        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
360        from a file.
361    
362    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
363        rounding is not applied in this particular case).
364    
365    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
366        if they appear, or are escaped, in patterns.
367    
368    10. Get rid of a number of -Wunused-but-set-variable warnings.
369    
370    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
371        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
372        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
373        also returns the mark "x". This bug applied to capturing parentheses,
374        non-capturing parentheses, and atomic parentheses. It also applied to some
375        assertions.
376    
377    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
378        information out of configure.ac instead of relying on pcre.h.generic, which
379        is not stored in the repository.
380    
381    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
382        -lreadline.
383    
384    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
385    
386    15. Applied Graycode's patch to put the top-level frame on the stack rather
387        than the heap when not using the stack for recursion. This gives a
388        performance improvement in many cases when recursion is not deep.
389    
390    16. Experimental code added to "pcretest -C" to output the stack frame size.
391    
392    
393  Version 8.21 12-Dec-2011  Version 8.21 12-Dec-2011
394  ------------------------  ------------------------

Legend:
Removed from v.836  
changed lines
  Added in v.1234

  ViewVC Help
Powered by ViewVC 1.1.5