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

Diff of /code/trunk/ChangeLog

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

revision 1431 by ph10, Thu Jan 2 17:41:28 2014 UTC revision 1520 by ph10, Sun Feb 8 16:29:23 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.35-RC1 xx-xxxx-201x  Version 8.37 xx-xxx-2015
5  -----------------------------  ------------------------
6    
7    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
8        for those parentheses to be closed with whatever has been captured so far.
9        However, it was failing to mark any other groups between the hightest
10        capture so far and the currrent group as "unset". Thus, the ovector for
11        those groups contained whatever was previously there. An example is the
12        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
13    
14    2.  If an assertion condition was quantified with a minimum of zero (an odd
15        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
16    
17    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
18        unrecognized modifier, a crash could occur.
19    
20    4.  An attempt to do global matching in pcretest with a zero-length ovector
21        caused a crash.
22    
23    5.  Fixed a memory leak during matching that could occur for a subpattern
24        subroutine call (recursive or otherwise) if the number of captured groups
25        that had to be saved was greater than ten.
26    
27    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
28        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
29        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
30    
31    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
32        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
33    
34    8. When a pattern is compiled, it remembers the highest back reference so that
35       when matching, if the ovector is too small, extra memory can be obtained to
36       use instead. A conditional subpattern whose condition is a check on a
37       capture having happened, such as, for example in the pattern
38       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
39       setting the highest backreference number. This mattered only if pcre_exec()
40       was called with an ovector that was too small to hold the capture, and there
41       was no other kind of back reference (a situation which is probably quite
42       rare). The effect of the bug was that the condition was always treated as
43       FALSE when the capture could not be consulted, leading to a incorrect
44       behaviour by pcre2_match(). This bug has been fixed.
45    
46    
47    Version 8.36 26-September-2014
48    ------------------------------
49    
50    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
51        -Wmissing-field-initializers and -Wunused-parameter.
52    
53    2.  The tests for quantifiers being too big (greater than 65535) were being
54        applied after reading the number, and stupidly assuming that integer
55        overflow would give a negative number. The tests are now applied as the
56        numbers are read.
57    
58    3.  Tidy code in pcre_exec.c where two branches that used to be different are
59        now the same.
60    
61    4.  The JIT compiler did not generate match limit checks for certain
62        bracketed expressions with quantifiers. This may lead to exponential
63        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
64        issue should be resolved now.
65    
66    5.  Fixed an issue, which occures when nested alternatives are optimized
67        with table jumps.
68    
69    6.  Inserted two casts and changed some ints to size_t in the light of some
70        reported 64-bit compiler warnings (Bugzilla 1477).
71    
72    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
73        an empty string, which sometimes were behaving incorrectly in the
74        interpreter (though correctly in the JIT matcher). This pcretest input is
75        an example:
76    
77          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
78          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
79    
80        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
81        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
82        for an empty string was breaking the inner loop and carrying on at a lower
83        level, when possessive repeated groups should always return to a higher
84        level as they have no backtrack points in them. The empty string test now
85        occurs at the outer level.
86    
87    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
88        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
89    
90    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
91        doesn't).
92    
93    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
94        to hold a pattern to be incorrectly computed (too small) when there were
95        named back references to duplicated names. This could cause "internal
96        error: code overflow" or "double free or corruption" or other memory
97        handling errors.
98    
99    11. When named subpatterns had the same prefixes, back references could be
100        confused. For example, in this pattern:
101    
102          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
103    
104        the reference to 'Name' was incorrectly treated as a reference to a
105        duplicate name.
106    
107    12. A pattern such as /^s?c/mi8 where the optional character has more than
108        one "other case" was incorrectly compiled such that it would only try to
109        match starting at "c".
110    
111    13. When a pattern starting with \s was studied, VT was not included in the
112        list of possible starting characters; this should have been part of the
113        8.34/18 patch.
114    
115    14. If a character class started [\Qx]... where x is any character, the class
116        was incorrectly terminated at the ].
117    
118    15. If a pattern that started with a caseless match for a character with more
119        than one "other case" was studied, PCRE did not set up the starting code
120        unit bit map for the list of possible characters. Now it does. This is an
121        optimization improvement, not a bug fix.
122    
123    16. The Unicode data tables have been updated to Unicode 7.0.0.
124    
125    17. Fixed a number of memory leaks in pcregrep.
126    
127    18. Avoid a compiler warning (from some compilers) for a function call with
128        a cast that removes "const" from an lvalue by using an intermediate
129        variable (to which the compiler does not object).
130    
131    19. Incorrect code was compiled if a group that contained an internal recursive
132        back reference was optional (had quantifier with a minimum of zero). This
133        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
134        caused segmentation faults because of stack overflows at compile time.
135    
136    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
137        group that is quantified with an indefinite repeat, caused a compile-time
138        loop which used up all the system stack and provoked a segmentation fault.
139        This was not the same bug as 19 above.
140    
141    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
142        Patch by Mike Frysinger.
143    
144    
145    Version 8.35 04-April-2014
146    --------------------------
147    
148  1.  A new flag is set, when property checks are present in an XCLASS.  1.  A new flag is set, when property checks are present in an XCLASS.
149      When this flag is not set, PCRE can perform certain optimizations      When this flag is not set, PCRE can perform certain optimizations
# Line 27  Version 8.35-RC1 xx-xxxx-201x Line 168  Version 8.35-RC1 xx-xxxx-201x
168    
169  6.  Improve character range checks in JIT. Characters are read by an inprecise  6.  Improve character range checks in JIT. Characters are read by an inprecise
170      function now, which returns with an unknown value if the character code is      function now, which returns with an unknown value if the character code is
171      above a certain treshold (e.g: 256). The only limitation is that the value      above a certain threshold (e.g: 256). The only limitation is that the value
172      must be bigger than the treshold as well. This function is useful, when      must be bigger than the threshold as well. This function is useful when
173      the characters above the treshold are handled in the same way.      the characters above the threshold are handled in the same way.
174    
175  7.  The macros whose names start with RAWUCHAR are placeholders for a future  7.  The macros whose names start with RAWUCHAR are placeholders for a future
176      mode in which only the bottom 21 bits of 32-bit data items are used. To      mode in which only the bottom 21 bits of 32-bit data items are used. To
177      make this more memorable for those maintaining the code, the names have      make this more memorable for those maintaining the code, the names have
178      been changed to start with UCHAR21, and an extensive comment has been added      been changed to start with UCHAR21, and an extensive comment has been added
179      to their definition.      to their definition.
180    
181    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
182        to the export list in Makefile.am (they were accidentally omitted from the
183        8.34 tarball).
184    
185    9.  The informational output from pcretest used the phrase "starting byte set"
186        which is inappropriate for the 16-bit and 32-bit libraries. As the output
187        for "first char" and "need char" really means "non-UTF-char", I've changed
188        "byte" to "char", and slightly reworded the output. The documentation about
189        these values has also been (I hope) clarified.
190    
191    10. Another JIT related optimization: use table jumps for selecting the correct
192        backtracking path, when more than four alternatives are present inside a
193        bracket.
194    
195    11. Empty match is not possible, when the minimum length is greater than zero,
196        and there is no \K in the pattern. JIT should avoid empty match checks in
197        such cases.
198    
199    12. In a caseless character class with UCP support, when a character with more
200        than one alternative case was not the first character of a range, not all
201        the alternative cases were added to the class. For example, s and \x{17f}
202        are both alternative cases for S: the class [RST] was handled correctly,
203        but [R-T] was not.
204    
205    13. The configure.ac file always checked for pthread support when JIT was
206        enabled. This is not used in Windows, so I have put this test inside a
207        check for the presence of windows.h (which was already tested for).
208    
209    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
210        The algorithm provides a way to skip certain starting offsets, and usually
211        faster than linear prefix searches.
212    
213    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
214        as for 'fr_FR' and 'french'. For some reason, however, it then used the
215        Windows-specific input and output files, which have 'french' screwed in.
216        So this could never have worked. One of the problems with locales is that
217        they aren't always the same. I have now updated RunTest so that it checks
218        the output of the locale test (test 3) against three different output
219        files, and it allows the test to pass if any one of them matches. With luck
220        this should make the test pass on some versions of Solaris where it was
221        failing. Because of the uncertainty, the script did not used to stop if
222        test 3 failed; it now does. If further versions of a French locale ever
223        come to light, they can now easily be added.
224    
225    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
226        there was a message during ./configure, but it did not stop. This now
227        provokes an error. The invalid example in README has been corrected.
228        If a value less than the minimum is given, the minimum value has always
229        been used, but now a warning is given.
230    
231    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
232        was a bug in the test system, which is now fixed. Also, the list of various
233        configurations that are tested for each release did not have one with both
234        16/32 bits and --enable-bar-anycrlf. It now does.
235    
236    18. pcretest was missing "-C bsr" for displaying the \R default setting.
237    
238    19. Little endian PowerPC systems are supported now by the JIT compiler.
239    
240    20. The fast forward newline mechanism could enter to an infinite loop on
241        certain invalid UTF-8 input. Although we don't support these cases
242        this issue can be fixed by a performance optimization.
243    
244    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
245        not take account if existing stack usage. There is now a new global
246        variable called pcre_stack_guard that can be set to point to an external
247        function to check stack availability. It is called at the start of
248        processing every parenthesized group.
249    
250    22. A typo in the code meant that in ungreedy mode the max/min qualifier
251        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
252        not match "ab".
253    
254    23. When UTF was disabled, the JIT program reported some incorrect compile
255        errors. These messages are silenced now.
256    
257    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
258        compiler.
259    
260    25. Change all the temporary files used in RunGrepTest to be different to those
261        used by RunTest so that the tests can be run simultaneously, for example by
262        "make -j check".
263    
264    
265  Version 8.34 15-December-2013  Version 8.34 15-December-2013

Legend:
Removed from v.1431  
changed lines
  Added in v.1520

  ViewVC Help
Powered by ViewVC 1.1.5