ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 977 by zherczeg, Sun Jun 17 06:20:52 2012 UTC revision 1248 by ph10, Wed Feb 13 17:36:38 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.31 02-June-2012  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.
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.
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
37    9.  Optimizing fast_forward_start_bits in JIT.
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
44        (b) Minimum length was not checked before the matching is started.
46        WARNING: Callouts are not release ready! <- this line needs to be removed when it is.
48    11. The value of capture_last that is passed to callouts was incorrect in some
49        cases when there was a capture on one path that was subsequently abandoned
50        after a backtrack. Also, the capture_last value is now reset after a
51        recursion, since all captures are also reset in this case.
53    12. The interpreter no longer returns the "too many substrings" error in the
54        case when an overflowing capture is in a branch that is subsequently
55        abandoned after a backtrack.
57    13. In the pathological case when an offset vector of size 2 is used, pcretest
58        now prints out the matched string after a yield of 0 or 1.
61    Version 8.32 30-November-2012
62    -----------------------------
64    1.  Improved JIT compiler optimizations for first character search and single
65        character iterators.
67    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
68        Patch by Daniel Richard G.
70    3.  Single character iterator optimizations in the JIT compiler.
72    4.  Improved JIT compiler optimizations for character ranges.
74    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
75        Reported by Giuseppe D'Angelo.
77    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
78        of a line, was being set incorrectly in cases where .* appeared inside
79        atomic brackets at the start of a pattern, or where there was a subsequent
80        *PRUNE or *SKIP.
82    7.  Improved instruction cache flush for POWER/PowerPC.
83        Patch by Daniel Richard G.
85    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
86        grep:
88        (a) There is now no limit to the number of patterns to be matched.
90        (b) An error is given if a pattern is too long.
92        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
93            are now supported.
95        (d) --exclude-from and --include-from (multiple use) have been added.
97        (e) Exclusions and inclusions now apply to all files and directories, not
98            just to those obtained from scanning a directory recursively.
100        (f) Multiple uses of -f and --file-list are now supported.
102        (g) In a Windows environment, the default for -d has been changed from
103            "read" (the GNU grep default) to "skip", because otherwise the presence
104            of a directory in the file list provokes an error.
106        (h) The documentation has been revised and clarified in places.
108    9.  Improve the matching speed of capturing brackets.
110    10. Changed the meaning of \X so that it now matches a Unicode extended
111        grapheme cluster.
113    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
114        out POSIX threads when JIT support is configured.
116    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
118    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
119        structure could go wrong in environments where size_t is not the same size
120        as int.
122    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
123        set.
125    15. The EBCDIC support had decayed; later updates to the code had included
126        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
127        general tidy up of EBCDIC-related issues, and the documentation was also
128        not quite right. There is now a test that can be run on ASCII systems to
129        check some of the EBCDIC-related things (but is it not a full test).
131    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
132        in a small tidy to the code.
134    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
136    18. If the --only-matching (-o) option in pcregrep is specified multiple
137        times, each one causes appropriate output. For example, -o1 -o2 outputs the
138        substrings matched by the 1st and 2nd capturing parentheses. A separating
139        string can be specified by --om-separator (default empty).
141    19. Improving the first n character searches.
143    20. Turn case lists for horizontal and vertical white space into macros so that
144        they are defined only once.
146    21. This set of changes together give more compatible Unicode case-folding
147        behaviour for characters that have more than one other case when UCP
148        support is available.
150        (a) The Unicode property table now has offsets into a new table of sets of
151            three or more characters that are case-equivalent. The MultiStage2.py
152            script that generates these tables (the pcre_ucd.c file) now scans
153            CaseFolding.txt instead of UnicodeData.txt for character case
154            information.
156        (b) The code for adding characters or ranges of characters to a character
157            class has been abstracted into a generalized function that also handles
158            case-independence. In UTF-mode with UCP support, this uses the new data
159            to handle characters with more than one other case.
161        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
162            whose other case is greater than 256 are now correctly matched
163            caselessly. Previously, the high codepoint matched the low one, but not
164            vice versa.
166        (d) The processing of \h, \H, \v, and \ in character classes now makes use
167            of the new class addition function, using character lists defined as
168            macros alongside the case definitions of 20 above.
170        (e) Caseless back references now work with characters that have more than
171            one other case.
173        (f) General caseless matching of characters with more than one other case
174            is supported.
176    22. Unicode character properties were updated from Unicode 6.2.0
178    23. Improved CMake support under Windows. Patch by Daniel Richard G.
180    24. Add support for 32-bit character strings, and UTF-32
182    25. Major JIT compiler update (code refactoring and bugfixing).
183        Experimental Sparc 32 support is added.
185    26. Applied a modified version of Daniel Richard G's patch to create
186        pcre.h.generic and config.h.generic by "make" instead of in the
187        PrepareRelease script.
189    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
190        pcre_compile.c when checking for a zero character.
192    28. Introducing a native interface for JIT. Through this interface, the compiled
193        machine code can be directly executed. The purpose of this interface is to
194        provide fast pattern matching, so several sanity checks are not performed.
195        However, feature tests are still performed. The new interface provides
196        1.4x speedup compared to the old one.
198    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
199        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
200        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
202    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
203        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
204        the "old" RFC 2279). Instead, it ended up passing a negative length to
205        pcre_exec().
207    31. Add support for GCC's visibility feature to hide internal functions.
209    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
210        "unknown -C option" after outputting 0 or 1.
212    33. There is now support for generating a code coverage report for the test
213        suite in environments where gcc is the compiler and lcov is installed. This
214        is mainly for the benefit of the developers.
216    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
217        unaddressable using valgrind annotations, allowing valgrind to detect
218        invalid memory accesses. This is mainly for the benefit of the developers.
220    25. (*UTF) can now be used to start a pattern in any of the three libraries.
222    26. Give configure error if --enable-cpp but no C++ compiler found.
225    Version 8.31 06-July-2012
226  -------------------------  -------------------------
228  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
# Line 132  Version 8.31 02-June-2012 Line 353  Version 8.31 02-June-2012
354  37. Optimizing single character iterators in JIT.  37. Optimizing single character iterators in JIT.
356    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
357        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
358        codepoints that are too big for the mode are faulted, and in a UTF mode,
359        disallowed codepoints are also faulted.
361    39. If PCRE was compiled with UTF support, in three places in the DFA
362        matcher there was code that should only have been obeyed in UTF mode, but
363        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
364        processing when bytes with values greater than 127 were present. In 16-bit
365        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
366        both cases the values are those that cannot be the first data item in a UTF
367        character. The three items that might have provoked this were recursions,
368        possessively repeated groups, and atomic groups.
370    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
371        and pcregrep, because some OS require shared objects to be explicitly
372        passed to ld, causing the link step to fail if they are not.
374    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
375        mode, patterns that started with \h* or \R* might be incorrectly matched.
378  Version 8.30 04-February-2012  Version 8.30 04-February-2012
379  -----------------------------  -----------------------------

Removed from v.977  
changed lines
  Added in v.1248

  ViewVC Help
Powered by ViewVC 1.1.5