ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 989 by zherczeg, Sat Jul 7 11:11:02 2012 UTC revision 1338 by zherczeg, Fri Jun 14 07:54:36 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.32  Version 8.34 xx-xxxx-201x
5  ------------  --------------------------
7    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8        executable memory. Patch inspired by Carsten Klein.
11    Version 8.33 28-May-2013
12    --------------------------
14    1.  Added 'U' to some constants that are compared to unsigned integers, to
15        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
16        variables that are added to signed variables, to ensure the result is
17        signed and can be negated.
19    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
20        CMake config files.
22    3.  Revise the creation of config.h.generic so that all boolean macros are
23        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
24        overriding via -D on the command line possible.
26    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
27        to unsigned int is reported to make a quite noticeable speed difference in
28        a specific Windows environment. Testing on Linux did also appear to show
29        some benefit (and it is clearly not harmful). Also fixed the definition of
30        Xop which should be unsigned.
32    5.  Related to (4), changing the definition of the intermediate variable cc
33        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
34        improvements.
36    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
37        unnecessary spaces.
39    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
40        and later.
42    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
44    9.  Optimizing fast_forward_start_bits in JIT.
46    10. Adding support for callouts in JIT, and fixing some issues revealed
47        during this work. Namely:
49        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
51        (b) Minimum length was not checked before the matching is started.
53    11. The value of capture_last that is passed to callouts was incorrect in some
54        cases when there was a capture on one path that was subsequently abandoned
55        after a backtrack. Also, the capture_last value is now reset after a
56        recursion, since all captures are also reset in this case.
58    12. The interpreter no longer returns the "too many substrings" error in the
59        case when an overflowing capture is in a branch that is subsequently
60        abandoned after a backtrack.
62    13. In the pathological case when an offset vector of size 2 is used, pcretest
63        now prints out the matched string after a yield of 0 or 1.
65    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
66        Only supported by the JIT compiler at the moment.
68    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
70    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
71        offset of the starting point of the matching process, provided the offsets
72        vector is large enough.
74    17. The \A escape now records a lookbehind value of 1, though its execution
75        does not actually inspect the previous character. This is to ensure that,
76        in partial multi-segment matching, at least one character from the old
77        segment is retained when a new segment is processed. Otherwise, if there
78        are no lookbehinds in the pattern, \A might match incorrectly at the start
79        of a new segment.
81    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
83    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
84        gives some modest performance improvement in 8-bit mode.
86    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
87        be expressed in certain programming languages using Universal Character
88        Names.
90    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
91        which points out that "non characters" are not "characters that may not
92        appear in Unicode strings" but rather "characters that are reserved for
93        internal use and have only local meaning".
95    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
96        there was a conditional group that depended on an assertion, if the
97        assertion was false, the callout that immediately followed the alternation
98        in the condition was skipped when pcre_exec() was used for matching.
100    23. Allow an explicit callout to be inserted before an assertion that is the
101        condition for a conditional group, for compatibility with automatic
102        callouts, which always insert a callout at this point.
104    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
105        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
107    25. (*PRUNE) is now supported by the JIT compiler.
109    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
111    27. Fix the case where there are two or more SKIPs with arguments that may be
112        ignored.
114    28. (*SKIP) is now supported by the JIT compiler.
116    29. (*THEN) is now supported by the JIT compiler.
118    30. Update RunTest with additional test selector options.
120    31. The way PCRE handles backtracking verbs has been changed in two ways.
122        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
123        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
124        backtracking. In some cases this makes it more Perl-compatible, but Perl's
125        rather obscure rules do not always do the same thing.
127        (2) Previously, backtracking verbs were confined within assertions. This is
128        no longer the case for positive assertions, except for (*ACCEPT). Again,
129        this sometimes improves Perl compatibility, and sometimes does not.
131    32. A number of tests that were in test 2 because Perl did things differently
132        have been moved to test 1, because either Perl or PCRE has changed, and
133        these tests are now compatible.
135    32. Backtracking control verbs are now handled in the same way in JIT and
136        interpreter.
138    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
139        contained a forward subroutine reference caused a compile error.
141    34. Auto-detect and optimize limited repetitions in JIT.
143    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
144        blocking (*UTF) etc.
146    36. In the interpreter, maximizing pattern repetitions for characters and
147        character types now use tail recursion, which reduces stack usage.
149    37. The value of the max lookbehind was not correctly preserved if a compiled
150        and saved regex was reloaded on a host of different endianness.
152    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
153        of the compiled pattern block, expand the flags field from 16 to 32 bits
154        because it was almost full.
156    39. Try madvise first before posix_madvise.
158    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
159        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
160        original change locked out all matches of empty strings. This has been
161        changed so that one match of an empty string per line is recognized.
162        Subsequent searches on the same line (for colouring or for --only-matching,
163        for example) do not recognize empty strings.
165    41. Applied a user patch to fix a number of spelling mistakes in comments.
167    42. Data lines longer than 65536 caused pcretest to crash.
169    43. Clarified the data type for length and startoffset arguments for pcre_exec
170        and pcre_dfa_exec in the function-specific man pages, where they were
171        explicitly stated to be in bytes, never having been updated. I also added
172        some clarification to the pcreapi man page.
174    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
175        a segmentation fault.
178    Version 8.32 30-November-2012
179    -----------------------------
181  1.  Improved JIT compiler optimizations for first character search and single  1.  Improved JIT compiler optimizations for first character search and single
182      character iterators.      character iterators.
# Line 12  Version 8.32 Line 186  Version 8.32
187  3.  Single character iterator optimizations in the JIT compiler.  3.  Single character iterator optimizations in the JIT compiler.
189    4.  Improved JIT compiler optimizations for character ranges.
191    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
192        Reported by Giuseppe D'Angelo.
194    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
195        of a line, was being set incorrectly in cases where .* appeared inside
196        atomic brackets at the start of a pattern, or where there was a subsequent
197        *PRUNE or *SKIP.
199    7.  Improved instruction cache flush for POWER/PowerPC.
200        Patch by Daniel Richard G.
202    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
203        grep:
205        (a) There is now no limit to the number of patterns to be matched.
207        (b) An error is given if a pattern is too long.
209        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
210            are now supported.
212        (d) --exclude-from and --include-from (multiple use) have been added.
214        (e) Exclusions and inclusions now apply to all files and directories, not
215            just to those obtained from scanning a directory recursively.
217        (f) Multiple uses of -f and --file-list are now supported.
219        (g) In a Windows environment, the default for -d has been changed from
220            "read" (the GNU grep default) to "skip", because otherwise the presence
221            of a directory in the file list provokes an error.
223        (h) The documentation has been revised and clarified in places.
225    9.  Improve the matching speed of capturing brackets.
227    10. Changed the meaning of \X so that it now matches a Unicode extended
228        grapheme cluster.
230    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
231        out POSIX threads when JIT support is configured.
233    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
235    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
236        structure could go wrong in environments where size_t is not the same size
237        as int.
239    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
240        set.
242    15. The EBCDIC support had decayed; later updates to the code had included
243        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
244        general tidy up of EBCDIC-related issues, and the documentation was also
245        not quite right. There is now a test that can be run on ASCII systems to
246        check some of the EBCDIC-related things (but is it not a full test).
248    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
249        in a small tidy to the code.
251    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
253    18. If the --only-matching (-o) option in pcregrep is specified multiple
254        times, each one causes appropriate output. For example, -o1 -o2 outputs the
255        substrings matched by the 1st and 2nd capturing parentheses. A separating
256        string can be specified by --om-separator (default empty).
258    19. Improving the first n character searches.
260    20. Turn case lists for horizontal and vertical white space into macros so that
261        they are defined only once.
263    21. This set of changes together give more compatible Unicode case-folding
264        behaviour for characters that have more than one other case when UCP
265        support is available.
267        (a) The Unicode property table now has offsets into a new table of sets of
268            three or more characters that are case-equivalent. The MultiStage2.py
269            script that generates these tables (the pcre_ucd.c file) now scans
270            CaseFolding.txt instead of UnicodeData.txt for character case
271            information.
273        (b) The code for adding characters or ranges of characters to a character
274            class has been abstracted into a generalized function that also handles
275            case-independence. In UTF-mode with UCP support, this uses the new data
276            to handle characters with more than one other case.
278        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
279            whose other case is greater than 256 are now correctly matched
280            caselessly. Previously, the high codepoint matched the low one, but not
281            vice versa.
283        (d) The processing of \h, \H, \v, and \ in character classes now makes use
284            of the new class addition function, using character lists defined as
285            macros alongside the case definitions of 20 above.
287        (e) Caseless back references now work with characters that have more than
288            one other case.
290        (f) General caseless matching of characters with more than one other case
291            is supported.
293    22. Unicode character properties were updated from Unicode 6.2.0
295    23. Improved CMake support under Windows. Patch by Daniel Richard G.
297    24. Add support for 32-bit character strings, and UTF-32
299    25. Major JIT compiler update (code refactoring and bugfixing).
300        Experimental Sparc 32 support is added.
302    26. Applied a modified version of Daniel Richard G's patch to create
303        pcre.h.generic and config.h.generic by "make" instead of in the
304        PrepareRelease script.
306    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
307        pcre_compile.c when checking for a zero character.
309    28. Introducing a native interface for JIT. Through this interface, the compiled
310        machine code can be directly executed. The purpose of this interface is to
311        provide fast pattern matching, so several sanity checks are not performed.
312        However, feature tests are still performed. The new interface provides
313        1.4x speedup compared to the old one.
315    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
316        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
317        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
319    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
320        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
321        the "old" RFC 2279). Instead, it ended up passing a negative length to
322        pcre_exec().
324    31. Add support for GCC's visibility feature to hide internal functions.
326    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
327        "unknown -C option" after outputting 0 or 1.
329    33. There is now support for generating a code coverage report for the test
330        suite in environments where gcc is the compiler and lcov is installed. This
331        is mainly for the benefit of the developers.
333    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
334        unaddressable using valgrind annotations, allowing valgrind to detect
335        invalid memory accesses. This is mainly for the benefit of the developers.
337    25. (*UTF) can now be used to start a pattern in any of the three libraries.
339    26. Give configure error if --enable-cpp but no C++ compiler found.
342  Version 8.31 06-July-2012  Version 8.31 06-July-2012
343  -------------------------  -------------------------
# Line 1356  Version 7.9 11-Apr-09 Line 1682  Version 7.9 11-Apr-09
1682  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1683      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1684      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1685      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1686        8.33.]
1688  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1689      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1599  Version 7.7 07-May-08 Line 1926  Version 7.7 07-May-08
1926      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
1927      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
1928      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
1929      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
1930      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
1931      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.989  
changed lines
  Added in v.1338

  ViewVC Help
Powered by ViewVC 1.1.5