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

Diff of /code/trunk/ChangeLog

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

revision 1450 by ph10, Fri Jan 17 17:50:51 2014 UTC revision 1496 by ph10, Fri Jul 18 08:24:35 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.35-RC1 xx-xxxx-201x  Version 8.36 xx-xxx-2014
5  -----------------------------  ------------------------
6    
7    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
8        -Wmissing-field-initializers and -Wunused-parameter.
9    
10    2.  The tests for quantifiers being too big (greater than 65535) were being
11        applied after reading the number, and stupidly assuming that integer
12        overflow would give a negative number. The tests are now applied as the
13        numbers are read.
14    
15    3.  Tidy code in pcre_exec.c where two branches that used to be different are
16        now the same.
17    
18    4.  The JIT compiler did not generate match limit checks for certain
19        bracketed expressions with quantifiers. This may lead to exponential
20        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
21        issue should be resolved now.
22    
23    5.  Fixed an issue, which occures when nested alternatives are optimized
24        with table jumps.
25    
26    6.  Inserted two casts and changed some ints to size_t in the light of some
27        reported 64-bit compiler warnings (Bugzilla 1477).
28    
29    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
30        an empty string, which sometimes were behaving incorrectly in the
31        interpreter (though correctly in the JIT matcher). This pcretest input is
32        an example:
33    
34          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
35          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
36    
37        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
38        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
39        for an empty string was breaking the inner loop and carrying on at a lower
40        level, when possessive repeated groups should always return to a higher
41        level as they have no backtrack points in them. The empty string test now
42        occurs at the outer level.
43    
44    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
45        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
46    
47    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
48        doesn't).
49    
50    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
51        to hold a pattern to be incorrectly computed (too small) when there were
52        named back references to duplicated names. This could cause "internal
53        error: code overflow" or "double free or corruption" or other memory
54        handling errors.
55    
56    11. When named subpatterns had the same prefixes, back references could be
57        confused. For example, in this pattern:
58    
59          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
60    
61        the reference to 'Name' was incorrectly treated as a reference to a
62        duplicate name.
63    
64    12. A pattern such as /^s?c/mi8 where the optional character has more than
65        one "other case" was incorrectly compiled such that it would only try to
66        match starting at "c".
67    
68    13. When a pattern starting with \s was studied, VT was not included in the
69        list of possible starting characters; this should have been part of the
70        8.34/18 patch.
71    
72    14. If a character class started [\Qx]... where x is any character, the class
73        was incorrectly terminated at the ].
74    
75    15. If a pattern that started with a caseless match for a character with more
76        than one "other case" was studied, PCRE did not set up the starting code
77        unit bit map for the list of possible characters. Now it does. This is an
78        optimization improvement, not a bug fix.
79    
80    16. The Unicode data tables have been updated to Unicode 7.0.0.
81    
82    17. Fixed a number of memory leaks in pcregrep.
83    
84    18. Avoid a compiler warning (from some compilers) for a function call with
85        a cast that removes "const" from an lvalue by using an intermediate
86        variable (to which the compiler does not object).
87    
88    19. Incorrect code was compiled if a group that contained an internal recursive
89        back reference was optional (had quantifier with a minimum of zero). This
90        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
91        caused segmentation faults because of stack overflows at compile time.
92    
93    
94    Version 8.35 04-April-2014
95    --------------------------
96    
97  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.
98      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 117  Version 8.35-RC1 xx-xxxx-201x
117    
118  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
119      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
120      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
121      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
122      the characters above the treshold are handled in the same way.      the characters above the threshold are handled in the same way.
123    
124  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
125      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
126      make this more memorable for those maintaining the code, the names have      make this more memorable for those maintaining the code, the names have
127      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
128      to their definition.      to their definition.
129    
130  8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c  8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
131      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
132      8.34 tarball).      8.34 tarball).
133    
134  9.  The informational output from pcretest used the phrase "starting byte set"  9.  The informational output from pcretest used the phrase "starting byte set"
135      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
136      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
137      "byte" to "char", and slightly reworded the output. The documentation about      "byte" to "char", and slightly reworded the output. The documentation about
138      these values has also been (I hope) clarified.      these values has also been (I hope) clarified.
139    
140  10. Another JIT related optimization: use table jumps for selecting the correct  10. Another JIT related optimization: use table jumps for selecting the correct
141      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 144  Version 8.35-RC1 xx-xxxx-201x
144  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,
145      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
146      such cases.      such cases.
147    
148  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
149      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
150      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}
151      are both alternative cases for S: the class [RST] was handled correctly,      are both alternative cases for S: the class [RST] was handled correctly,
152      but [R-T] was not.      but [R-T] was not.
153    
154  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
155      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
156      check for the presence of windows.h (which was already tested for).      check for the presence of windows.h (which was already tested for).
157    
158  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.
159      The algorithm provides a way to skip certain starting offsets, and usually      The algorithm provides a way to skip certain starting offsets, and usually
160      faster than linear prefix searches.      faster than linear prefix searches.
161    
162  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
163      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
164      Windows-specific input and output files, which have 'french' screwed in.      Windows-specific input and output files, which have 'french' screwed in.
165      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
166      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
167      the output of the locale test (test 3) against three different output      the output of the locale test (test 3) against three different output
168      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
169      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
170      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
171      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
172      come to light, they can now easily be added.      come to light, they can now easily be added.
173    
174  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",
175      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
176      provokes an error. The invalid example in README has been corrected.      provokes an error. The invalid example in README has been corrected.
177      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
178      been used, but now a warning is given.      been used, but now a warning is given.
179    
180  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
181      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
182      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
183      16/32 bits and --enable-bar-anycrlf. It now does.      16/32 bits and --enable-bar-anycrlf. It now does.
184    
185  18. pcretest was missing "-C bsr" for displaying the \R default setting.  18. pcretest was missing "-C bsr" for displaying the \R default setting.
186    
187    19. Little endian PowerPC systems are supported now by the JIT compiler.
188    
189    20. The fast forward newline mechanism could enter to an infinite loop on
190        certain invalid UTF-8 input. Although we don't support these cases
191        this issue can be fixed by a performance optimization.
192    
193    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
194        not take account if existing stack usage. There is now a new global
195        variable called pcre_stack_guard that can be set to point to an external
196        function to check stack availability. It is called at the start of
197        processing every parenthesized group.
198    
199    22. A typo in the code meant that in ungreedy mode the max/min qualifier
200        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
201        not match "ab".
202    
203    23. When UTF was disabled, the JIT program reported some incorrect compile
204        errors. These messages are silenced now.
205    
206    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
207        compiler.
208    
209    25. Change all the temporary files used in RunGrepTest to be different to those
210        used by RunTest so that the tests can be run simultaneously, for example by
211        "make -j check".
212    
213    
214  Version 8.34 15-December-2013  Version 8.34 15-December-2013

Legend:
Removed from v.1450  
changed lines
  Added in v.1496

  ViewVC Help
Powered by ViewVC 1.1.5