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

Diff of /code/trunk/ChangeLog

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

revision 740 by zherczeg, Mon Oct 31 06:10:14 2011 UTC revision 994 by ph10, Tue Jul 10 14:29:26 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.21  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    
26    Version 8.31 06-July-2012
27    -------------------------
28    
29    1.  Fixing a wrong JIT test case and some compiler warnings.
30    
31    2.  Removed a bashism from the RunTest script.
32    
33    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
34        to unsigned type, result still unsigned" that was given by an MS compiler
35        on encountering the code "-sizeof(xxx)".
36    
37    4.  Partial matching support is added to the JIT compiler.
38    
39    5.  Fixed several bugs concerned with partial matching of items that consist
40        of more than one character:
41    
42        (a) /^(..)\1/ did not partially match "aba" because checking references was
43            done on an "all or nothing" basis. This also applied to repeated
44            references.
45    
46        (b) \R did not give a hard partial match if \r was found at the end of the
47            subject.
48    
49        (c) \X did not give a hard partial match after matching one or more
50            characters at the end of the subject.
51    
52        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
53            a partial match for the string "\r".
54    
55        (e) When newline was set to CRLF, the metacharacter "." did not recognize
56            a partial match for a CR character at the end of the subject string.
57    
58    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
59        running pcretest, the text "(JIT)" added to the output whenever JIT is
60        actually used to run the match.
61    
62    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
63        or /S+[+] with a digit between 1 and 7.
64    
65    8.  OP_NOT now supports any UTF character not just single-byte ones.
66    
67    9.  (*MARK) control verb is now supported by the JIT compiler.
68    
69    10. The command "./RunTest list" lists the available tests without actually
70        running any of them. (Because I keep forgetting what they all are.)
71    
72    11. Add PCRE_INFO_MAXLOOKBEHIND.
73    
74    12. Applied a (slightly modified) user-supplied patch that improves performance
75        when the heap is used for recursion (compiled with --disable-stack-for-
76        recursion). Instead of malloc and free for each heap frame each time a
77        logical recursion happens, frames are retained on a chain and re-used where
78        possible. This sometimes gives as much as 30% improvement.
79    
80    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
81        call.
82    
83    14. As documented, (*COMMIT) is now confined to within a positive assertion.
84    
85    15. It is now possible to link pcretest with libedit as an alternative to
86        libreadline.
87    
88    16. (*COMMIT) control verb is now supported by the JIT compiler.
89    
90    17. The Unicode data tables have been updated to Unicode 6.1.0.
91    
92    18. Added --file-list option to pcregrep.
93    
94    19. Added binary file support to pcregrep, including the -a, --binary-files,
95        -I, and --text options.
96    
97    20. The madvise function is renamed for posix_madvise for QNX compatibility
98        reasons. Fixed by Giuseppe D'Angelo.
99    
100    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
101    
102    22. Changed the option for creating symbolic links for 16-bit man pages from
103        -s to -sf so that re-installing does not cause issues.
104    
105    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
106    
107    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
108        matches in certain environments (the workspace was not being correctly
109        retained). Also added to pcre_dfa_exec() a simple plausibility check on
110        some of the workspace data at the beginning of a restart.
111    
112    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
113        was not doing so when it should - probably a typo introduced by SVN 528
114        (change 8.10/14).
115    
116    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
117        \w+ when the character tables indicated that \x{c4} was a word character.
118        There were several related cases, all because the tests for doing a table
119        lookup were testing for characters less than 127 instead of 255.
120    
121    27. If a pattern contains capturing parentheses that are not used in a match,
122        their slots in the ovector are set to -1. For those that are higher than
123        any matched groups, this happens at the end of processing. In the case when
124        there were back references that the ovector was too small to contain
125        (causing temporary malloc'd memory to be used during matching), and the
126        highest capturing number was not used, memory off the end of the ovector
127        was incorrectly being set to -1. (It was using the size of the temporary
128        memory instead of the true size.)
129    
130    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
131        ovector size, it uses memory at the end of the block that it has got.
132    
133    29. Check for an overlong MARK name and give an error at compile time. The
134        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
135    
136    30. JIT compiler update.
137    
138    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
139        Rill for the patch.
140    
141    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
142    
143    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
144    
145    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
146        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
147        was enabled.
148    
149    35. Improve JIT code generation for greedy plus quantifier.
150    
151    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
152        1 to "aa" instead of to an empty string. The bug affected repeated groups
153        that could potentially match an empty string.
154    
155    37. Optimizing single character iterators in JIT.
156    
157    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
158        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
159        codepoints that are too big for the mode are faulted, and in a UTF mode,
160        disallowed codepoints are also faulted.
161    
162    39. If PCRE was compiled with UTF support, in three places in the DFA
163        matcher there was code that should only have been obeyed in UTF mode, but
164        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
165        processing when bytes with values greater than 127 were present. In 16-bit
166        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
167        both cases the values are those that cannot be the first data item in a UTF
168        character. The three items that might have provoked this were recursions,
169        possessively repeated groups, and atomic groups.
170    
171    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
172        and pcregrep, because some OS require shared objects to be explicitly
173        passed to ld, causing the link step to fail if they are not.
174    
175    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
176        mode, patterns that started with \h* or \R* might be incorrectly matched.
177    
178    
179    Version 8.30 04-February-2012
180    -----------------------------
181    
182    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
183        name is defined in ctype.h.
184    
185    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
186        only in quite long subpatterns.
187    
188    3.  Removed the function pcre_info(), which has been obsolete and deprecated
189        since it was replaced by pcre_fullinfo() in February 2000.
190    
191    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
192        match a (*MARK), and the match failed at the start of the subject, a
193        reference to memory before the start of the subject could occur. This bug
194        was introduced by fix 17 of release 8.21.
195    
196    5.  A reference to an unset group with zero minimum repetition was giving
197        totally wrong answers (in non-JavaScript-compatibility mode). For example,
198        /(another)?(\1?)test/ matched against "hello world test". This bug was
199        introduced in release 8.13.
200    
201    6.  Add support for 16-bit character strings (a large amount of work involving
202        many changes and refactorings).
203    
204    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
205        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
206        from a file.
207    
208    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
209        rounding is not applied in this particular case).
210    
211    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
212        if they appear, or are escaped, in patterns.
213    
214    10. Get rid of a number of -Wunused-but-set-variable warnings.
215    
216    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
217        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
218        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
219        also returns the mark "x". This bug applied to capturing parentheses,
220        non-capturing parentheses, and atomic parentheses. It also applied to some
221        assertions.
222    
223    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
224        information out of configure.ac instead of relying on pcre.h.generic, which
225        is not stored in the repository.
226    
227    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
228        -lreadline.
229    
230    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
231    
232    15. Applied Graycode's patch to put the top-level frame on the stack rather
233        than the heap when not using the stack for recursion. This gives a
234        performance improvement in many cases when recursion is not deep.
235    
236    16. Experimental code added to "pcretest -C" to output the stack frame size.
237    
238    
239    Version 8.21 12-Dec-2011
240    ------------------------
241    
242  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
243    
244    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
245        are added as well.
246    
247    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
248        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
249        calling _pcre_jit_exec. Some extra comments are added.
250    
251    4.  (*MARK) settings inside atomic groups that do not contain any capturing
252        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
253        was introduced by change 18 for 8.20.
254    
255    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
256        ECMA-262 standard.
257    
258    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
259        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
260        This bug was probably introduced by change 9 of 8.13.
261    
262    7.  While fixing 6 above, I noticed that a number of other items were being
263        incorrectly rejected as "not fixed length". This arose partly because newer
264        opcodes had not been added to the fixed-length checking code. I have (a)
265        corrected the bug and added tests for these items, and (b) arranged for an
266        error to occur if an unknown opcode is encountered while checking for fixed
267        length instead of just assuming "not fixed length". The items that were
268        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
269        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
270        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
271    
272    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
273        being incorrectly compiled and would have given unpredicatble results.
274    
275    9.  A possessively repeated subpattern with minimum repeat count greater than
276        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
277        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
278        the first (A) could occur when it should not.
279    
280    10. Add a cast and remove a redundant test from the code.
281    
282    11. JIT should use pcre_malloc/pcre_free for allocation.
283    
284    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
285        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
286        is anything other than /usr, -L is still shown).
287    
288    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
289    
290    14. Perl does not support \N without a following name in a [] class; PCRE now
291        also gives an error.
292    
293    15. If a forward reference was repeated with an upper limit of around 2000,
294        it caused the error "internal error: overran compiling workspace". The
295        maximum number of forward references (including repeats) was limited by the
296        internal workspace, and dependent on the LINK_SIZE. The code has been
297        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
298        the default depends on LINK_SIZE. There is a new upper limit (for safety)
299        of around 200,000 forward references. While doing this, I also speeded up
300        the filling in of repeated forward references.
301    
302    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
303        incorrectly expecting the subject to contain another "a" after the start.
304    
305    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
306        in the match, the SKIP should be ignored. This was not happening; instead
307        the SKIP was being treated as NOMATCH. For patterns such as
308        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
309        tested.
310    
311    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
312        now much more compatible with Perl, in particular in cases where the result
313        is a non-match for a non-anchored pattern. For example, if
314        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
315        "m", where previously it did not return a name. A side effect of this
316        change is that for partial matches, the last encountered mark name is
317        returned, as for non matches. A number of tests that were previously not
318        Perl-compatible have been moved into the Perl-compatible test files. The
319        refactoring has had the pleasing side effect of removing one argument from
320        the match() function, thus reducing its stack requirements.
321    
322    19. If the /S+ option was used in pcretest to study a pattern using JIT,
323        subsequent uses of /S (without +) incorrectly behaved like /S+.
324    
325    21. Retrieve executable code size support for the JIT compiler and fixing
326        some warnings.
327    
328    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
329        not work when the shorter character appeared right at the end of the
330        subject string.
331    
332    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
333        systems.
334    
335    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
336        output it when the /M option is used in pcretest.
337    
338    25. The CheckMan script was not being included in the distribution. Also, added
339        an explicit "perl" to run Perl scripts from the PrepareRelease script
340        because this is reportedly needed in Windows.
341    
342    26. If study data was being save in a file and studying had not found a set of
343        "starts with" bytes for the pattern, the data written to the file (though
344        never used) was taken from uninitialized memory and so caused valgrind to
345        complain.
346    
347    27. Updated RunTest.bat as provided by Sheri Pierce.
348    
349    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
350    
351    29. Computation of memory usage for the table of capturing group names was
352        giving an unnecessarily large value.
353    
354    
355  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
356  ------------------------  ------------------------

Legend:
Removed from v.740  
changed lines
  Added in v.994

  ViewVC Help
Powered by ViewVC 1.1.5