version 1.1.1.3, 2012/10/09 09:19:17
|
version 1.1.1.4, 2013/07/22 08:25:55
|
Line 1
|
Line 1
|
ChangeLog for PCRE |
ChangeLog for PCRE |
------------------ |
------------------ |
|
|
|
Version 8.33 28-May-2013 |
|
-------------------------- |
|
|
|
1. Added 'U' to some constants that are compared to unsigned integers, to |
|
avoid compiler signed/unsigned warnings. Added (int) casts to unsigned |
|
variables that are added to signed variables, to ensure the result is |
|
signed and can be negated. |
|
|
|
2. Applied patch by Daniel Richard G for quashing MSVC warnings to the |
|
CMake config files. |
|
|
|
3. Revise the creation of config.h.generic so that all boolean macros are |
|
#undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes |
|
overriding via -D on the command line possible. |
|
|
|
4. Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar |
|
to unsigned int is reported to make a quite noticeable speed difference in |
|
a specific Windows environment. Testing on Linux did also appear to show |
|
some benefit (and it is clearly not harmful). Also fixed the definition of |
|
Xop which should be unsigned. |
|
|
|
5. Related to (4), changing the definition of the intermediate variable cc |
|
in repeated character loops from pcre_uchar to pcre_uint32 also gave speed |
|
improvements. |
|
|
|
6. Fix forward search in JIT when link size is 3 or greater. Also removed some |
|
unnecessary spaces. |
|
|
|
7. Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12 |
|
and later. |
|
|
|
8. Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only. |
|
|
|
9. Optimizing fast_forward_start_bits in JIT. |
|
|
|
10. Adding support for callouts in JIT, and fixing some issues revealed |
|
during this work. Namely: |
|
|
|
(a) Unoptimized capturing brackets incorrectly reset on backtrack. |
|
|
|
(b) Minimum length was not checked before the matching is started. |
|
|
|
11. The value of capture_last that is passed to callouts was incorrect in some |
|
cases when there was a capture on one path that was subsequently abandoned |
|
after a backtrack. Also, the capture_last value is now reset after a |
|
recursion, since all captures are also reset in this case. |
|
|
|
12. The interpreter no longer returns the "too many substrings" error in the |
|
case when an overflowing capture is in a branch that is subsequently |
|
abandoned after a backtrack. |
|
|
|
13. In the pathological case when an offset vector of size 2 is used, pcretest |
|
now prints out the matched string after a yield of 0 or 1. |
|
|
|
14. Inlining subpatterns in recursions, when certain conditions are fulfilled. |
|
Only supported by the JIT compiler at the moment. |
|
|
|
15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez. |
|
|
|
16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the |
|
offset of the starting point of the matching process, provided the offsets |
|
vector is large enough. |
|
|
|
17. The \A escape now records a lookbehind value of 1, though its execution |
|
does not actually inspect the previous character. This is to ensure that, |
|
in partial multi-segment matching, at least one character from the old |
|
segment is retained when a new segment is processed. Otherwise, if there |
|
are no lookbehinds in the pattern, \A might match incorrectly at the start |
|
of a new segment. |
|
|
|
18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations. |
|
|
|
19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this |
|
gives some modest performance improvement in 8-bit mode. |
|
|
|
20. Added the PCRE-specific property \p{Xuc} for matching characters that can |
|
be expressed in certain programming languages using Universal Character |
|
Names. |
|
|
|
21. Unicode validation has been updated in the light of Unicode Corrigendum #9, |
|
which points out that "non characters" are not "characters that may not |
|
appear in Unicode strings" but rather "characters that are reserved for |
|
internal use and have only local meaning". |
|
|
|
22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and |
|
there was a conditional group that depended on an assertion, if the |
|
assertion was false, the callout that immediately followed the alternation |
|
in the condition was skipped when pcre_exec() was used for matching. |
|
|
|
23. Allow an explicit callout to be inserted before an assertion that is the |
|
condition for a conditional group, for compatibility with automatic |
|
callouts, which always insert a callout at this point. |
|
|
|
24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also |
|
confines (*SKIP) and (*PRUNE) in the same way, and this has now been done. |
|
|
|
25. (*PRUNE) is now supported by the JIT compiler. |
|
|
|
26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa. |
|
|
|
27. Fix the case where there are two or more SKIPs with arguments that may be |
|
ignored. |
|
|
|
28. (*SKIP) is now supported by the JIT compiler. |
|
|
|
29. (*THEN) is now supported by the JIT compiler. |
|
|
|
30. Update RunTest with additional test selector options. |
|
|
|
31. The way PCRE handles backtracking verbs has been changed in two ways. |
|
|
|
(1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override |
|
SKIP. Now, PCRE acts on whichever backtracking verb is reached first by |
|
backtracking. In some cases this makes it more Perl-compatible, but Perl's |
|
rather obscure rules do not always do the same thing. |
|
|
|
(2) Previously, backtracking verbs were confined within assertions. This is |
|
no longer the case for positive assertions, except for (*ACCEPT). Again, |
|
this sometimes improves Perl compatibility, and sometimes does not. |
|
|
|
32. A number of tests that were in test 2 because Perl did things differently |
|
have been moved to test 1, because either Perl or PCRE has changed, and |
|
these tests are now compatible. |
|
|
|
32. Backtracking control verbs are now handled in the same way in JIT and |
|
interpreter. |
|
|
|
33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that |
|
contained a forward subroutine reference caused a compile error. |
|
|
|
34. Auto-detect and optimize limited repetitions in JIT. |
|
|
|
35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular, |
|
blocking (*UTF) etc. |
|
|
|
36. In the interpreter, maximizing pattern repetitions for characters and |
|
character types now use tail recursion, which reduces stack usage. |
|
|
|
37. The value of the max lookbehind was not correctly preserved if a compiled |
|
and saved regex was reloaded on a host of different endianness. |
|
|
|
38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension |
|
of the compiled pattern block, expand the flags field from 16 to 32 bits |
|
because it was almost full. |
|
|
|
39. Try madvise first before posix_madvise. |
|
|
|
40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines |
|
with a pattern such as ^$. It has taken 4 years for anybody to notice! The |
|
original change locked out all matches of empty strings. This has been |
|
changed so that one match of an empty string per line is recognized. |
|
Subsequent searches on the same line (for colouring or for --only-matching, |
|
for example) do not recognize empty strings. |
|
|
|
41. Applied a user patch to fix a number of spelling mistakes in comments. |
|
|
|
42. Data lines longer than 65536 caused pcretest to crash. |
|
|
|
43. Clarified the data type for length and startoffset arguments for pcre_exec |
|
and pcre_dfa_exec in the function-specific man pages, where they were |
|
explicitly stated to be in bytes, never having been updated. I also added |
|
some clarification to the pcreapi man page. |
|
|
|
44. A call to pcre_dfa_exec() with an output vector size less than 2 caused |
|
a segmentation fault. |
|
|
|
|
|
Version 8.32 30-November-2012 |
|
----------------------------- |
|
|
|
1. Improved JIT compiler optimizations for first character search and single |
|
character iterators. |
|
|
|
2. Supporting IBM XL C compilers for PPC architectures in the JIT compiler. |
|
Patch by Daniel Richard G. |
|
|
|
3. Single character iterator optimizations in the JIT compiler. |
|
|
|
4. Improved JIT compiler optimizations for character ranges. |
|
|
|
5. Rename the "leave" variable names to "quit" to improve WinCE compatibility. |
|
Reported by Giuseppe D'Angelo. |
|
|
|
6. The PCRE_STARTLINE bit, indicating that a match can occur only at the start |
|
of a line, was being set incorrectly in cases where .* appeared inside |
|
atomic brackets at the start of a pattern, or where there was a subsequent |
|
*PRUNE or *SKIP. |
|
|
|
7. Improved instruction cache flush for POWER/PowerPC. |
|
Patch by Daniel Richard G. |
|
|
|
8. Fixed a number of issues in pcregrep, making it more compatible with GNU |
|
grep: |
|
|
|
(a) There is now no limit to the number of patterns to be matched. |
|
|
|
(b) An error is given if a pattern is too long. |
|
|
|
(c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir |
|
are now supported. |
|
|
|
(d) --exclude-from and --include-from (multiple use) have been added. |
|
|
|
(e) Exclusions and inclusions now apply to all files and directories, not |
|
just to those obtained from scanning a directory recursively. |
|
|
|
(f) Multiple uses of -f and --file-list are now supported. |
|
|
|
(g) In a Windows environment, the default for -d has been changed from |
|
"read" (the GNU grep default) to "skip", because otherwise the presence |
|
of a directory in the file list provokes an error. |
|
|
|
(h) The documentation has been revised and clarified in places. |
|
|
|
9. Improve the matching speed of capturing brackets. |
|
|
|
10. Changed the meaning of \X so that it now matches a Unicode extended |
|
grapheme cluster. |
|
|
|
11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting |
|
out POSIX threads when JIT support is configured. |
|
|
|
12. Added support for PCRE_STUDY_EXTRA_NEEDED. |
|
|
|
13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg |
|
structure could go wrong in environments where size_t is not the same size |
|
as int. |
|
|
|
14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be |
|
set. |
|
|
|
15. The EBCDIC support had decayed; later updates to the code had included |
|
explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a |
|
general tidy up of EBCDIC-related issues, and the documentation was also |
|
not quite right. There is now a test that can be run on ASCII systems to |
|
check some of the EBCDIC-related things (but is it not a full test). |
|
|
|
16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting |
|
in a small tidy to the code. |
|
|
|
17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled. |
|
|
|
18. If the --only-matching (-o) option in pcregrep is specified multiple |
|
times, each one causes appropriate output. For example, -o1 -o2 outputs the |
|
substrings matched by the 1st and 2nd capturing parentheses. A separating |
|
string can be specified by --om-separator (default empty). |
|
|
|
19. Improving the first n character searches. |
|
|
|
20. Turn case lists for horizontal and vertical white space into macros so that |
|
they are defined only once. |
|
|
|
21. This set of changes together give more compatible Unicode case-folding |
|
behaviour for characters that have more than one other case when UCP |
|
support is available. |
|
|
|
(a) The Unicode property table now has offsets into a new table of sets of |
|
three or more characters that are case-equivalent. The MultiStage2.py |
|
script that generates these tables (the pcre_ucd.c file) now scans |
|
CaseFolding.txt instead of UnicodeData.txt for character case |
|
information. |
|
|
|
(b) The code for adding characters or ranges of characters to a character |
|
class has been abstracted into a generalized function that also handles |
|
case-independence. In UTF-mode with UCP support, this uses the new data |
|
to handle characters with more than one other case. |
|
|
|
(c) A bug that is fixed as a result of (b) is that codepoints less than 256 |
|
whose other case is greater than 256 are now correctly matched |
|
caselessly. Previously, the high codepoint matched the low one, but not |
|
vice versa. |
|
|
|
(d) The processing of \h, \H, \v, and \ in character classes now makes use |
|
of the new class addition function, using character lists defined as |
|
macros alongside the case definitions of 20 above. |
|
|
|
(e) Caseless back references now work with characters that have more than |
|
one other case. |
|
|
|
(f) General caseless matching of characters with more than one other case |
|
is supported. |
|
|
|
22. Unicode character properties were updated from Unicode 6.2.0 |
|
|
|
23. Improved CMake support under Windows. Patch by Daniel Richard G. |
|
|
|
24. Add support for 32-bit character strings, and UTF-32 |
|
|
|
25. Major JIT compiler update (code refactoring and bugfixing). |
|
Experimental Sparc 32 support is added. |
|
|
|
26. Applied a modified version of Daniel Richard G's patch to create |
|
pcre.h.generic and config.h.generic by "make" instead of in the |
|
PrepareRelease script. |
|
|
|
27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in |
|
pcre_compile.c when checking for a zero character. |
|
|
|
28. Introducing a native interface for JIT. Through this interface, the compiled |
|
machine code can be directly executed. The purpose of this interface is to |
|
provide fast pattern matching, so several sanity checks are not performed. |
|
However, feature tests are still performed. The new interface provides |
|
1.4x speedup compared to the old one. |
|
|
|
29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for |
|
the subject string length, the error given was PCRE_ERROR_BADOFFSET, which |
|
was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case. |
|
|
|
30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints |
|
greater than 0x7fffffff (which cannot be represented in UTF-8, even under |
|
the "old" RFC 2279). Instead, it ended up passing a negative length to |
|
pcre_exec(). |
|
|
|
31. Add support for GCC's visibility feature to hide internal functions. |
|
|
|
32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error |
|
"unknown -C option" after outputting 0 or 1. |
|
|
|
33. There is now support for generating a code coverage report for the test |
|
suite in environments where gcc is the compiler and lcov is installed. This |
|
is mainly for the benefit of the developers. |
|
|
|
34. If PCRE is built with --enable-valgrind, certain memory regions are marked |
|
unaddressable using valgrind annotations, allowing valgrind to detect |
|
invalid memory accesses. This is mainly for the benefit of the developers. |
|
|
|
25. (*UTF) can now be used to start a pattern in any of the three libraries. |
|
|
|
26. Give configure error if --enable-cpp but no C++ compiler found. |
|
|
|
|
Version 8.31 06-July-2012 |
Version 8.31 06-July-2012 |
------------------------- |
------------------------- |
|
|
Line 1344 Version 7.9 11-Apr-09
|
Line 1675 Version 7.9 11-Apr-09
|
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 |
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 |
locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this |
locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this |
seems to be how GNU grep behaves. | seems to be how GNU grep behaves. [But see later change 40 for release |
| 8.33.] |
|
|
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 |
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 1587 Version 7.7 07-May-08
|
Line 1919 Version 7.7 07-May-08
|
containing () gave an internal compiling error instead of "reference to |
containing () gave an internal compiling error instead of "reference to |
non-existent subpattern". Fortunately, when the pattern did exist, the |
non-existent subpattern". Fortunately, when the pattern did exist, the |
compiled code was correct. (When scanning forwards to check for the |
compiled code was correct. (When scanning forwards to check for the |
existencd of the subpattern, it was treating the data ']' as terminating | existence of the subpattern, it was treating the data ']' as terminating |
the class, so got the count wrong. When actually compiling, the reference |
the class, so got the count wrong. When actually compiling, the reference |
was subsequently set up correctly.) |
was subsequently set up correctly.) |
|
|