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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.742  
changed lines
  Added in v.1025

  ViewVC Help
Powered by ViewVC 1.1.5