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

Diff of /code/trunk/ChangeLog

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

revision 931 by ph10, Fri Feb 24 13:21:02 2012 UTC revision 1039 by ph10, Thu Sep 13 16:39:03 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31  Version 8.32
5  -----------------------------  ------------
6    
7    1.  Improved JIT compiler optimizations for first character search and single
8        character iterators.
9    
10    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
11        Patch by Daniel Richard G.
12    
13    3.  Single character iterator optimizations in the JIT compiler.
14    
15    4.  Improved JIT compiler optimizations for character ranges.
16    
17    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
18        Reported by Giuseppe D'Angelo.
19    
20    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
21        of a line, was being set incorrectly in cases where .* appeared inside
22        atomic brackets at the start of a pattern, or where there was a subsequent
23        *PRUNE or *SKIP.
24    
25    7.  Improved instruction cache flush for POWER/PowerPC.
26        Patch by Daniel Richard G.
27    
28    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
29        grep:
30    
31        (a) There is now no limit to the number of patterns to be matched.
32    
33        (b) An error is given if a pattern is too long.
34    
35        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
36            are now supported.
37    
38        (d) --exclude-from and --include-from (multiple use) have been added.
39    
40        (e) Exclusions and inclusions now apply to all files and directories, not
41            just to those obtained from scanning a directory recursively.
42    
43        (f) Multiple uses of -f and --file-list are now supported.
44    
45        (g) In a Windows environment, the default for -d has been changed from
46            "read" (the GNU grep default) to "skip", because otherwise the presence
47            of a directory in the file list provokes an error.
48    
49        (h) The documentation has been revised and clarified in places.
50    
51    9.  Improve the matching speed of capturing brackets.
52    
53    10. Changed the meaning of \X so that it now matches a Unicode extended
54        grapheme cluster.
55    
56    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
57        out POSIX threads when JIT support is configured.
58    
59    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
60    
61    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
62        structure could go wrong in environments where size_t is not the same size
63        as int.
64    
65    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
66        set.
67    
68    15. The EBCDIC support had decayed; later updates to the code had included
69        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
70        general tidy up of EBCDIC-related issues, and the documentation was also
71        not quite right. There is now a test that can be run on ASCII systems to
72        check some of the EBCDIC-related things (but is it not a full test).
73    
74    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
75        in a small tidy to the code.
76    
77    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
78    
79    18. If the --only-matching (-o) option in pcregrep is specified multiple
80        times, each one causes appropriate output. For example, -o1 -o2 outputs the
81        substrings matched by the 1st and 2nd capturing parentheses. A separating
82        string can be specified by --om-separator (default empty).
83    
84    
85    Version 8.31 06-July-2012
86    -------------------------
87    
88  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
89    
90  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
91    
92  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
93      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
94      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
95    
96  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
# Line 18  Version 8.31 Line 99  Version 8.31
99      of more than one character:      of more than one character:
100    
101      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
102          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
103          references.          references.
104    
105      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
106          subject.          subject.
107    
108      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
109          characters at the end of the subject.          characters at the end of the subject.
110    
111      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
# Line 33  Version 8.31 Line 114  Version 8.31
114      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
115          a partial match for a CR character at the end of the subject string.          a partial match for a CR character at the end of the subject string.
116    
117  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
118      running pcretest, the text "(JIT)" added to the output whenever JIT is      running pcretest, the text "(JIT)" added to the output whenever JIT is
119      actually used to run the match.      actually used to run the match.
120    
121  7.  Individual JIT compile options can be set in pcretest by following -s+[+]  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
122      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
123    
124  8.  OP_NOT now supports any UTF character not just single-byte ones.  8.  OP_NOT now supports any UTF character not just single-byte ones.
# Line 47  Version 8.31 Line 128  Version 8.31
128  10. The command "./RunTest list" lists the available tests without actually  10. The command "./RunTest list" lists the available tests without actually
129      running any of them. (Because I keep forgetting what they all are.)      running any of them. (Because I keep forgetting what they all are.)
130    
131    11. Add PCRE_INFO_MAXLOOKBEHIND.
132    
133    12. Applied a (slightly modified) user-supplied patch that improves performance
134        when the heap is used for recursion (compiled with --disable-stack-for-
135        recursion). Instead of malloc and free for each heap frame each time a
136        logical recursion happens, frames are retained on a chain and re-used where
137        possible. This sometimes gives as much as 30% improvement.
138    
139    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
140        call.
141    
142    14. As documented, (*COMMIT) is now confined to within a positive assertion.
143    
144    15. It is now possible to link pcretest with libedit as an alternative to
145        libreadline.
146    
147    16. (*COMMIT) control verb is now supported by the JIT compiler.
148    
149    17. The Unicode data tables have been updated to Unicode 6.1.0.
150    
151    18. Added --file-list option to pcregrep.
152    
153    19. Added binary file support to pcregrep, including the -a, --binary-files,
154        -I, and --text options.
155    
156    20. The madvise function is renamed for posix_madvise for QNX compatibility
157        reasons. Fixed by Giuseppe D'Angelo.
158    
159    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
160    
161    22. Changed the option for creating symbolic links for 16-bit man pages from
162        -s to -sf so that re-installing does not cause issues.
163    
164    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
165    
166    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
167        matches in certain environments (the workspace was not being correctly
168        retained). Also added to pcre_dfa_exec() a simple plausibility check on
169        some of the workspace data at the beginning of a restart.
170    
171    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
172        was not doing so when it should - probably a typo introduced by SVN 528
173        (change 8.10/14).
174    
175    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
176        \w+ when the character tables indicated that \x{c4} was a word character.
177        There were several related cases, all because the tests for doing a table
178        lookup were testing for characters less than 127 instead of 255.
179    
180    27. If a pattern contains capturing parentheses that are not used in a match,
181        their slots in the ovector are set to -1. For those that are higher than
182        any matched groups, this happens at the end of processing. In the case when
183        there were back references that the ovector was too small to contain
184        (causing temporary malloc'd memory to be used during matching), and the
185        highest capturing number was not used, memory off the end of the ovector
186        was incorrectly being set to -1. (It was using the size of the temporary
187        memory instead of the true size.)
188    
189    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
190        ovector size, it uses memory at the end of the block that it has got.
191    
192    29. Check for an overlong MARK name and give an error at compile time. The
193        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
194    
195    30. JIT compiler update.
196    
197    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
198        Rill for the patch.
199    
200    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
201    
202    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
203    
204    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
205        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
206        was enabled.
207    
208    35. Improve JIT code generation for greedy plus quantifier.
209    
210    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
211        1 to "aa" instead of to an empty string. The bug affected repeated groups
212        that could potentially match an empty string.
213    
214    37. Optimizing single character iterators in JIT.
215    
216    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
217        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
218        codepoints that are too big for the mode are faulted, and in a UTF mode,
219        disallowed codepoints are also faulted.
220    
221    39. If PCRE was compiled with UTF support, in three places in the DFA
222        matcher there was code that should only have been obeyed in UTF mode, but
223        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
224        processing when bytes with values greater than 127 were present. In 16-bit
225        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
226        both cases the values are those that cannot be the first data item in a UTF
227        character. The three items that might have provoked this were recursions,
228        possessively repeated groups, and atomic groups.
229    
230    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
231        and pcregrep, because some OS require shared objects to be explicitly
232        passed to ld, causing the link step to fail if they are not.
233    
234    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
235        mode, patterns that started with \h* or \R* might be incorrectly matched.
236    
237    
238  Version 8.30 04-February-2012  Version 8.30 04-February-2012
239  -----------------------------  -----------------------------

Legend:
Removed from v.931  
changed lines
  Added in v.1039

  ViewVC Help
Powered by ViewVC 1.1.5