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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1454  
changed lines
  Added in v.1515

  ViewVC Help
Powered by ViewVC 1.1.5