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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.751  
changed lines
  Added in v.991

  ViewVC Help
Powered by ViewVC 1.1.5