ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.913  
changed lines
  Added in v.1236

  ViewVC Help
Powered by ViewVC 1.1.5