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

Diff of /code/trunk/ChangeLog

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

revision 1394 by ph10, Sat Nov 9 09:17:20 2013 UTC revision 1623 by zherczeg, Thu Feb 4 17:13:10 2016 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.34 xx-xxxx-201x  Note that the PCRE 8.xx series (PCRE1) is now in a bugfix-only state. All
5    development is happening in the PCRE2 10.xx series.
6    
7    Version 8.39 xx-xxxxxx-201x
8    ---------------------------
9    
10    1.  If PCRE_AUTO_CALLOUT was set on a pattern that had a (?# comment between
11        an item and its qualifier (for example, A(?#comment)?B) pcre_compile()
12        misbehaved. This bug was found by the LLVM fuzzer.
13    
14    2.  Similar to the above, if an isolated \E was present between an item and its
15        qualifier when PCRE_AUTO_CALLOUT was set, pcre_compile() misbehaved. This
16        bug was found by the LLVM fuzzer.
17    
18    3.  Further to 8.38/46, negated classes such as [^[:^ascii:]\d] were also not
19        working correctly in UCP mode.
20    
21    4.  The POSIX wrapper function regexec() crashed if the option REG_STARTEND
22        was set when the pmatch argument was NULL. It now returns REG_INVARG.
23    
24    5.  Allow for up to 32-bit numbers in the ordin() function in pcregrep.
25    
26    6.  An empty \Q\E sequence between an item and its qualifier caused
27        pcre_compile() to misbehave when auto callouts were enabled. This bug was
28        found by the LLVM fuzzer.
29    
30    7.  If a pattern that was compiled with PCRE_EXTENDED started with white
31        space or a #-type comment that was followed by (?-x), which turns off
32        PCRE_EXTENDED, and there was no subsequent (?x) to turn it on again,
33        pcre_compile() assumed that (?-x) applied to the whole pattern and
34        consequently mis-compiled it. This bug was found by the LLVM fuzzer.
35    
36    8.  An call of pcre_copy_named_substring() for a named substring whose number
37        was greater than the space in the ovector could cause a crash.
38    
39    9.  Yet another buffer overflow bug involved duplicate named groups with a
40        group that reset capture numbers (compare 8.38/7 below). Once again, I have
41        just allowed for more memory, even if not needed. (A proper fix is
42        implemented in PCRE2, but it involves a lot of refactoring.)
43    
44    10. pcre_get_substring_list() crashed if the use of \K in a match caused the
45        start of the match to be earlier than the end.
46    
47    11. JIT code generator for assertion matching is refactored to a separate
48        function.
49    
50    
51    Version 8.38 23-November-2015
52    -----------------------------
53    
54    1.  If a group that contained a recursive back reference also contained a
55        forward reference subroutine call followed by a non-forward-reference
56        subroutine call, for example /.((?2)(?R)\1)()/, pcre_compile() failed to
57        compile correct code, leading to undefined behaviour or an internally
58        detected error. This bug was discovered by the LLVM fuzzer.
59    
60    2.  Quantification of certain items (e.g. atomic back references) could cause
61        incorrect code to be compiled when recursive forward references were
62        involved. For example, in this pattern: /(?1)()((((((\1++))\x85)+)|))/.
63        This bug was discovered by the LLVM fuzzer.
64    
65    3.  A repeated conditional group whose condition was a reference by name caused
66        a buffer overflow if there was more than one group with the given name.
67        This bug was discovered by the LLVM fuzzer.
68    
69    4.  A recursive back reference by name within a group that had the same name as
70        another group caused a buffer overflow. For example:
71        /(?J)(?'d'(?'d'\g{d}))/. This bug was discovered by the LLVM fuzzer.
72    
73    5.  A forward reference by name to a group whose number is the same as the
74        current group, for example in this pattern: /(?|(\k'Pm')|(?'Pm'))/, caused
75        a buffer overflow at compile time. This bug was discovered by the LLVM
76        fuzzer.
77    
78    6.  A lookbehind assertion within a set of mutually recursive subpatterns could
79        provoke a buffer overflow. This bug was discovered by the LLVM fuzzer.
80    
81    7.  Another buffer overflow bug involved duplicate named groups with a
82        reference between their definition, with a group that reset capture
83        numbers, for example: /(?J:(?|(?'R')(\k'R')|((?'R'))))/. This has been
84        fixed by always allowing for more memory, even if not needed. (A proper fix
85        is implemented in PCRE2, but it involves more refactoring.)
86    
87    8.  There was no check for integer overflow in subroutine calls such as (?123).
88    
89    9.  The table entry for \l in EBCDIC environments was incorrect, leading to its
90        being treated as a literal 'l' instead of causing an error.
91    
92    10. There was a buffer overflow if pcre_exec() was called with an ovector of
93        size 1. This bug was found by american fuzzy lop.
94    
95    11. If a non-capturing group containing a conditional group that could match
96        an empty string was repeated, it was not identified as matching an empty
97        string itself. For example: /^(?:(?(1)x|)+)+$()/.
98    
99    12. In an EBCDIC environment, pcretest was mishandling the escape sequences
100        \a and \e in test subject lines.
101    
102    13. In an EBCDIC environment, \a in a pattern was converted to the ASCII
103        instead of the EBCDIC value.
104    
105    14. The handling of \c in an EBCDIC environment has been revised so that it is
106        now compatible with the specification in Perl's perlebcdic page.
107    
108    15. The EBCDIC character 0x41 is a non-breaking space, equivalent to 0xa0 in
109        ASCII/Unicode. This has now been added to the list of characters that are
110        recognized as white space in EBCDIC.
111    
112    16. When PCRE was compiled without UCP support, the use of \p and \P gave an
113        error (correctly) when used outside a class, but did not give an error
114        within a class.
115    
116    17. \h within a class was incorrectly compiled in EBCDIC environments.
117    
118    18. A pattern with an unmatched closing parenthesis that contained a backward
119        assertion which itself contained a forward reference caused buffer
120        overflow. And example pattern is: /(?=di(?<=(?1))|(?=(.))))/.
121    
122    19. JIT should return with error when the compiled pattern requires more stack
123        space than the maximum.
124    
125    20. A possessively repeated conditional group that could match an empty string,
126        for example, /(?(R))*+/, was incorrectly compiled.
127    
128    21. Fix infinite recursion in the JIT compiler when certain patterns such as
129        /(?:|a|){100}x/ are analysed.
130    
131    22. Some patterns with character classes involving [: and \\ were incorrectly
132        compiled and could cause reading from uninitialized memory or an incorrect
133        error diagnosis.
134    
135    23. Pathological patterns containing many nested occurrences of [: caused
136        pcre_compile() to run for a very long time.
137    
138    24. A conditional group with only one branch has an implicit empty alternative
139        branch and must therefore be treated as potentially matching an empty
140        string.
141    
142    25. If (?R was followed by - or + incorrect behaviour happened instead of a
143        diagnostic.
144    
145    26. Arrange to give up on finding the minimum matching length for overly
146        complex patterns.
147    
148    27. Similar to (4) above: in a pattern with duplicated named groups and an
149        occurrence of (?| it is possible for an apparently non-recursive back
150        reference to become recursive if a later named group with the relevant
151        number is encountered. This could lead to a buffer overflow. Wen Guanxing
152        from Venustech ADLAB discovered this bug.
153    
154    28. If pcregrep was given the -q option with -c or -l, or when handling a
155        binary file, it incorrectly wrote output to stdout.
156    
157    29. The JIT compiler did not restore the control verb head in case of *THEN
158        control verbs. This issue was found by Karl Skomski with a custom LLVM
159        fuzzer.
160    
161    30. Error messages for syntax errors following \g and \k were giving inaccurate
162        offsets in the pattern.
163    
164    31. Added a check for integer overflow in conditions (?(<digits>) and
165        (?(R<digits>). This omission was discovered by Karl Skomski with the LLVM
166        fuzzer.
167    
168    32. Handling recursive references such as (?2) when the reference is to a group
169        later in the pattern uses code that is very hacked about and error-prone.
170        It has been re-written for PCRE2. Here in PCRE1, a check has been added to
171        give an internal error if it is obvious that compiling has gone wrong.
172    
173    33. The JIT compiler should not check repeats after a {0,1} repeat byte code.
174        This issue was found by Karl Skomski with a custom LLVM fuzzer.
175    
176    34. The JIT compiler should restore the control chain for empty possessive
177        repeats. This issue was found by Karl Skomski with a custom LLVM fuzzer.
178    
179    35. Match limit check added to JIT recursion. This issue was found by Karl
180        Skomski with a custom LLVM fuzzer.
181    
182    36. Yet another case similar to 27 above has been circumvented by an
183        unconditional allocation of extra memory. This issue is fixed "properly" in
184        PCRE2 by refactoring the way references are handled. Wen Guanxing
185        from Venustech ADLAB discovered this bug.
186    
187    37. Fix two assertion fails in JIT. These issues were found by Karl Skomski
188        with a custom LLVM fuzzer.
189    
190    38. Fixed a corner case of range optimization in JIT.
191    
192    39. An incorrect error "overran compiling workspace" was given if there were
193        exactly enough group forward references such that the last one extended
194        into the workspace safety margin. The next one would have expanded the
195        workspace. The test for overflow was not including the safety margin.
196    
197    40. A match limit issue is fixed in JIT which was found by Karl Skomski
198        with a custom LLVM fuzzer.
199    
200    41. Remove the use of /dev/null in testdata/testinput2, because it doesn't
201        work under Windows. (Why has it taken so long for anyone to notice?)
202    
203    42. In a character class such as [\W\p{Any}] where both a negative-type escape
204        ("not a word character") and a property escape were present, the property
205        escape was being ignored.
206    
207    43. Fix crash caused by very long (*MARK) or (*THEN) names.
208    
209    44. A sequence such as [[:punct:]b] that is, a POSIX character class followed
210        by a single ASCII character in a class item, was incorrectly compiled in
211        UCP mode. The POSIX class got lost, but only if the single character
212        followed it.
213    
214    45. [:punct:] in UCP mode was matching some characters in the range 128-255
215        that should not have been matched.
216    
217    46. If [:^ascii:] or [:^xdigit:] or [:^cntrl:] are present in a non-negated
218        class, all characters with code points greater than 255 are in the class.
219        When a Unicode property was also in the class (if PCRE_UCP is set, escapes
220        such as \w are turned into Unicode properties), wide characters were not
221        correctly handled, and could fail to match.
222    
223    
224    Version 8.37 28-April-2015
225  --------------------------  --------------------------
226    
227    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
228        for those parentheses to be closed with whatever has been captured so far.
229        However, it was failing to mark any other groups between the hightest
230        capture so far and the currrent group as "unset". Thus, the ovector for
231        those groups contained whatever was previously there. An example is the
232        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
233    
234    2.  If an assertion condition was quantified with a minimum of zero (an odd
235        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
236    
237    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
238        unrecognized modifier, a crash could occur.
239    
240    4.  An attempt to do global matching in pcretest with a zero-length ovector
241        caused a crash.
242    
243    5.  Fixed a memory leak during matching that could occur for a subpattern
244        subroutine call (recursive or otherwise) if the number of captured groups
245        that had to be saved was greater than ten.
246    
247    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
248        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
249        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
250    
251    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
252        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
253    
254    8. When a pattern is compiled, it remembers the highest back reference so that
255       when matching, if the ovector is too small, extra memory can be obtained to
256       use instead. A conditional subpattern whose condition is a check on a
257       capture having happened, such as, for example in the pattern
258       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
259       setting the highest backreference number. This mattered only if pcre_exec()
260       was called with an ovector that was too small to hold the capture, and there
261       was no other kind of back reference (a situation which is probably quite
262       rare). The effect of the bug was that the condition was always treated as
263       FALSE when the capture could not be consulted, leading to a incorrect
264       behaviour by pcre_exec(). This bug has been fixed.
265    
266    9. A reference to a duplicated named group (either a back reference or a test
267       for being set in a conditional) that occurred in a part of the pattern where
268       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
269       to be incorrectly calculated, leading to overwriting.
270    
271    10. A mutually recursive set of back references such as (\2)(\1) caused a
272        segfault at study time (while trying to find the minimum matching length).
273        The infinite loop is now broken (with the minimum length unset, that is,
274        zero).
275    
276    11. If an assertion that was used as a condition was quantified with a minimum
277        of zero, matching went wrong. In particular, if the whole group had
278        unlimited repetition and could match an empty string, a segfault was
279        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
280        assertions to be quantified, but not if they are being used as conditions,
281        so the above pattern is faulted by Perl. PCRE has now been changed so that
282        it also rejects such patterns.
283    
284    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
285        failed to allow the zero-repeat case if pcre2_exec() was called with an
286        ovector too small to capture the group.
287    
288    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
289        Red Hat Product Security:
290    
291        (a) A crash if /K and /F were both set with the option to save the compiled
292        pattern.
293    
294        (b) Another crash if the option to print captured substrings in a callout
295        was combined with setting a null ovector, for example \O\C+ as a subject
296        string.
297    
298    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
299        forward reference repeated a large (but limited) number of times within a
300        repeated outer group that has a zero minimum quantifier, caused incorrect
301        code to be compiled, leading to the error "internal error:
302        previously-checked referenced subpattern not found" when an incorrect
303        memory address was read. This bug was reported as "heap overflow",
304        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
305        CVE-2015-2325.
306    
307    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
308        call within a group that also contained a recursive back reference caused
309        incorrect code to be compiled. This bug was reported as "heap overflow",
310        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
311        number CVE-2015-2326.
312    
313    24. Computing the size of the JIT read-only data in advance has been a source
314        of various issues, and new ones are still appear unfortunately. To fix
315        existing and future issues, size computation is eliminated from the code,
316        and replaced by on-demand memory allocation.
317    
318    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
319        adjacent to the end of the range, and the range contained characters with
320        more than one other case, caused incorrect behaviour when compiled in UTF
321        mode. In that example, the range a-j was left out of the class.
322    
323    26. Fix JIT compilation of conditional blocks, which assertion
324        is converted to (*FAIL). E.g: /(?(?!))/.
325    
326    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
327        discovered by the LLVM fuzzer.
328    
329    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
330        when this assertion was used as a condition, for example (?(?!)a|b). In
331        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
332        error about an unsupported item.
333    
334    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
335        possessification code could take exponential time to complete. A recursion
336        depth limit of 1000 has been imposed to limit the resources used by this
337        optimization.
338    
339    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
340        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
341        because \S ensures they are all in the class. The code for doing this was
342        interacting badly with the code for computing the amount of space needed to
343        compile the pattern, leading to a buffer overflow. This bug was discovered
344        by the LLVM fuzzer.
345    
346    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
347        other kinds of group caused stack overflow at compile time. This bug was
348        discovered by the LLVM fuzzer.
349    
350    32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
351        between a subroutine call and its quantifier was incorrectly compiled,
352        leading to buffer overflow or other errors. This bug was discovered by the
353        LLVM fuzzer.
354    
355    33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
356        assertion after (?(. The code was failing to check the character after
357        (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
358        was discovered by the LLVM fuzzer.
359    
360    34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
361        a fixed maximum following a group that contains a subroutine reference was
362        incorrectly compiled and could trigger buffer overflow. This bug was
363        discovered by the LLVM fuzzer.
364    
365    35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
366        caused a stack overflow instead of the diagnosis of a non-fixed length
367        lookbehind assertion. This bug was discovered by the LLVM fuzzer.
368    
369    36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
370        (e.g. /(?<=\Ka)/) could make pcregrep loop.
371    
372    37. There was a similar problem to 36 in pcretest for global matches.
373    
374    38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
375        and a subsequent item in the pattern caused a non-match, backtracking over
376        the repeated \X did not stop, but carried on past the start of the subject,
377        causing reference to random memory and/or a segfault. There were also some
378        other cases where backtracking after \C could crash. This set of bugs was
379        discovered by the LLVM fuzzer.
380    
381    39. The function for finding the minimum length of a matching string could take
382        a very long time if mutual recursion was present many times in a pattern,
383        for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
384        method has been implemented. This infelicity was discovered by the LLVM
385        fuzzer.
386    
387    40. Static linking against the PCRE library using the pkg-config module was
388        failing on missing pthread symbols.
389    
390    
391    Version 8.36 26-September-2014
392    ------------------------------
393    
394    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
395        -Wmissing-field-initializers and -Wunused-parameter.
396    
397    2.  The tests for quantifiers being too big (greater than 65535) were being
398        applied after reading the number, and stupidly assuming that integer
399        overflow would give a negative number. The tests are now applied as the
400        numbers are read.
401    
402    3.  Tidy code in pcre_exec.c where two branches that used to be different are
403        now the same.
404    
405    4.  The JIT compiler did not generate match limit checks for certain
406        bracketed expressions with quantifiers. This may lead to exponential
407        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
408        issue should be resolved now.
409    
410    5.  Fixed an issue, which occures when nested alternatives are optimized
411        with table jumps.
412    
413    6.  Inserted two casts and changed some ints to size_t in the light of some
414        reported 64-bit compiler warnings (Bugzilla 1477).
415    
416    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
417        an empty string, which sometimes were behaving incorrectly in the
418        interpreter (though correctly in the JIT matcher). This pcretest input is
419        an example:
420    
421          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
422          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
423    
424        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
425        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
426        for an empty string was breaking the inner loop and carrying on at a lower
427        level, when possessive repeated groups should always return to a higher
428        level as they have no backtrack points in them. The empty string test now
429        occurs at the outer level.
430    
431    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
432        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
433    
434    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
435        doesn't).
436    
437    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
438        to hold a pattern to be incorrectly computed (too small) when there were
439        named back references to duplicated names. This could cause "internal
440        error: code overflow" or "double free or corruption" or other memory
441        handling errors.
442    
443    11. When named subpatterns had the same prefixes, back references could be
444        confused. For example, in this pattern:
445    
446          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
447    
448        the reference to 'Name' was incorrectly treated as a reference to a
449        duplicate name.
450    
451    12. A pattern such as /^s?c/mi8 where the optional character has more than
452        one "other case" was incorrectly compiled such that it would only try to
453        match starting at "c".
454    
455    13. When a pattern starting with \s was studied, VT was not included in the
456        list of possible starting characters; this should have been part of the
457        8.34/18 patch.
458    
459    14. If a character class started [\Qx]... where x is any character, the class
460        was incorrectly terminated at the ].
461    
462    15. If a pattern that started with a caseless match for a character with more
463        than one "other case" was studied, PCRE did not set up the starting code
464        unit bit map for the list of possible characters. Now it does. This is an
465        optimization improvement, not a bug fix.
466    
467    16. The Unicode data tables have been updated to Unicode 7.0.0.
468    
469    17. Fixed a number of memory leaks in pcregrep.
470    
471    18. Avoid a compiler warning (from some compilers) for a function call with
472        a cast that removes "const" from an lvalue by using an intermediate
473        variable (to which the compiler does not object).
474    
475    19. Incorrect code was compiled if a group that contained an internal recursive
476        back reference was optional (had quantifier with a minimum of zero). This
477        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
478        caused segmentation faults because of stack overflows at compile time.
479    
480    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
481        group that is quantified with an indefinite repeat, caused a compile-time
482        loop which used up all the system stack and provoked a segmentation fault.
483        This was not the same bug as 19 above.
484    
485    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
486        Patch by Mike Frysinger.
487    
488    
489    Version 8.35 04-April-2014
490    --------------------------
491    
492    1.  A new flag is set, when property checks are present in an XCLASS.
493        When this flag is not set, PCRE can perform certain optimizations
494        such as studying these XCLASS-es.
495    
496    2.  The auto-possessification of character sets were improved: a normal
497        and an extended character set can be compared now. Furthermore
498        the JIT compiler optimizes more character set checks.
499    
500    3.  Got rid of some compiler warnings for potentially uninitialized variables
501        that show up only when compiled with -O2.
502    
503    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
504        of a match later then the end of the match. The pcretest program was not
505        handling the case sensibly - it was outputting from the start to the next
506        binary zero. It now reports this situation in a message, and outputs the
507        text from the end to the start.
508    
509    5.  Fast forward search is improved in JIT. Instead of the first three
510        characters, any three characters with fixed position can be searched.
511        Search order: first, last, middle.
512    
513    6.  Improve character range checks in JIT. Characters are read by an inprecise
514        function now, which returns with an unknown value if the character code is
515        above a certain threshold (e.g: 256). The only limitation is that the value
516        must be bigger than the threshold as well. This function is useful when
517        the characters above the threshold are handled in the same way.
518    
519    7.  The macros whose names start with RAWUCHAR are placeholders for a future
520        mode in which only the bottom 21 bits of 32-bit data items are used. To
521        make this more memorable for those maintaining the code, the names have
522        been changed to start with UCHAR21, and an extensive comment has been added
523        to their definition.
524    
525    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
526        to the export list in Makefile.am (they were accidentally omitted from the
527        8.34 tarball).
528    
529    9.  The informational output from pcretest used the phrase "starting byte set"
530        which is inappropriate for the 16-bit and 32-bit libraries. As the output
531        for "first char" and "need char" really means "non-UTF-char", I've changed
532        "byte" to "char", and slightly reworded the output. The documentation about
533        these values has also been (I hope) clarified.
534    
535    10. Another JIT related optimization: use table jumps for selecting the correct
536        backtracking path, when more than four alternatives are present inside a
537        bracket.
538    
539    11. Empty match is not possible, when the minimum length is greater than zero,
540        and there is no \K in the pattern. JIT should avoid empty match checks in
541        such cases.
542    
543    12. In a caseless character class with UCP support, when a character with more
544        than one alternative case was not the first character of a range, not all
545        the alternative cases were added to the class. For example, s and \x{17f}
546        are both alternative cases for S: the class [RST] was handled correctly,
547        but [R-T] was not.
548    
549    13. The configure.ac file always checked for pthread support when JIT was
550        enabled. This is not used in Windows, so I have put this test inside a
551        check for the presence of windows.h (which was already tested for).
552    
553    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
554        The algorithm provides a way to skip certain starting offsets, and usually
555        faster than linear prefix searches.
556    
557    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
558        as for 'fr_FR' and 'french'. For some reason, however, it then used the
559        Windows-specific input and output files, which have 'french' screwed in.
560        So this could never have worked. One of the problems with locales is that
561        they aren't always the same. I have now updated RunTest so that it checks
562        the output of the locale test (test 3) against three different output
563        files, and it allows the test to pass if any one of them matches. With luck
564        this should make the test pass on some versions of Solaris where it was
565        failing. Because of the uncertainty, the script did not used to stop if
566        test 3 failed; it now does. If further versions of a French locale ever
567        come to light, they can now easily be added.
568    
569    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
570        there was a message during ./configure, but it did not stop. This now
571        provokes an error. The invalid example in README has been corrected.
572        If a value less than the minimum is given, the minimum value has always
573        been used, but now a warning is given.
574    
575    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
576        was a bug in the test system, which is now fixed. Also, the list of various
577        configurations that are tested for each release did not have one with both
578        16/32 bits and --enable-bar-anycrlf. It now does.
579    
580    18. pcretest was missing "-C bsr" for displaying the \R default setting.
581    
582    19. Little endian PowerPC systems are supported now by the JIT compiler.
583    
584    20. The fast forward newline mechanism could enter to an infinite loop on
585        certain invalid UTF-8 input. Although we don't support these cases
586        this issue can be fixed by a performance optimization.
587    
588    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
589        not take account if existing stack usage. There is now a new global
590        variable called pcre_stack_guard that can be set to point to an external
591        function to check stack availability. It is called at the start of
592        processing every parenthesized group.
593    
594    22. A typo in the code meant that in ungreedy mode the max/min qualifier
595        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
596        not match "ab".
597    
598    23. When UTF was disabled, the JIT program reported some incorrect compile
599        errors. These messages are silenced now.
600    
601    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
602        compiler.
603    
604    25. Change all the temporary files used in RunGrepTest to be different to those
605        used by RunTest so that the tests can be run simultaneously, for example by
606        "make -j check".
607    
608    
609    Version 8.34 15-December-2013
610    -----------------------------
611    
612  1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT  1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
613      executable memory. Patch inspired by Carsten Klein.      executable memory. Patch inspired by Carsten Klein.
614    
615  2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although  2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
616      this macro is never tested and has no effect, because the work to support      this macro is never tested and has no effect, because the work to support
617      coverage involves only compiling and linking options and special targets in      coverage involves only compiling and linking options and special targets in
618      the Makefile. The comment in config.h implied that defining the macro would      the Makefile. The comment in config.h implied that defining the macro would
619      enable coverage support, which is totally false. There was also support for      enable coverage support, which is totally false. There was also support for
620      setting this macro in the CMake files (my fault, I just copied it from      setting this macro in the CMake files (my fault, I just copied it from
621      configure). SUPPORT_GCOV has now been removed.      configure). SUPPORT_GCOV has now been removed.
622    
623  3.  Make a small performance improvement in strlen16() and strlen32() in  3.  Make a small performance improvement in strlen16() and strlen32() in
624      pcretest.      pcretest.
625    
626  4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,  4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
627      detected by the Solaris compiler (gcc doesn't seem to be able to diagnose      detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
628      these cases). There was also one in pcretest.c.      these cases). There was also one in pcretest.c.
629    
630  5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.  5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
631    
632  6.  In UTF mode, the code for checking whether a group could match an empty  6.  In UTF mode, the code for checking whether a group could match an empty
633      string (which is used for indefinitely repeated groups to allow for      string (which is used for indefinitely repeated groups to allow for
# Line 31  Version 8.34 xx-xxxx-201x Line 636  Version 8.34 xx-xxxx-201x
636      data item and had a minimum repetition of zero (for example, [^\x{100}]* in      data item and had a minimum repetition of zero (for example, [^\x{100}]* in
637      UTF-8 mode). The effect was undefined: the group might or might not be      UTF-8 mode). The effect was undefined: the group might or might not be
638      deemed as matching an empty string, or the program might have crashed.      deemed as matching an empty string, or the program might have crashed.
639    
640  7.  The code for checking whether a group could match an empty string was not  7.  The code for checking whether a group could match an empty string was not
641      recognizing that \h, \H, \v, \V, and \R must match a character.      recognizing that \h, \H, \v, \V, and \R must match a character.
642    
643  8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match  8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
644      an empty string. If it can, pcretest shows this in its information output.      an empty string. If it can, pcretest shows this in its information output.
645    
646  9.  Fixed two related bugs that applied to Unicode extended grapheme clusters  9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
647      that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when      that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
648      matched by pcre_exec() without using JIT:      matched by pcre_exec() without using JIT:
649    
650      (a) If the rest of the pattern did not match after a maximal run of      (a) If the rest of the pattern did not match after a maximal run of
651          grapheme clusters, the code for backing up to try with fewer of them          grapheme clusters, the code for backing up to try with fewer of them
652          did not always back up over a full grapheme when characters that do not          did not always back up over a full grapheme when characters that do not
653          have the modifier quality were involved, e.g. Hangul syllables.          have the modifier quality were involved, e.g. Hangul syllables.
654    
655      (b) If the match point in a subject started with modifier character, and      (b) If the match point in a subject started with modifier character, and
656          there was no match, the code could incorrectly back up beyond the match          there was no match, the code could incorrectly back up beyond the match
657          point, and potentially beyond the first character in the subject,          point, and potentially beyond the first character in the subject,
658          leading to a segfault or an incorrect match result.          leading to a segfault or an incorrect match result.
659    
660  10. A conditional group with an assertion condition could lead to PCRE  10. A conditional group with an assertion condition could lead to PCRE
661      recording an incorrect first data item for a match if no other first data      recording an incorrect first data item for a match if no other first data
662      item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a      item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
663      first data item, and therefore matched "ca" after "c" instead of at the      first data item, and therefore matched "ca" after "c" instead of at the
664      start.      start.
665    
666  11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a  11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
667      bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.      bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
668    
669  12. The source of pcregrep now includes z/OS-specific code so that it can be  12. The source of pcregrep now includes z/OS-specific code so that it can be
670      compiled for z/OS as part of the special z/OS distribution.      compiled for z/OS as part of the special z/OS distribution.
671    
672  13. Added the -T and -TM options to pcretest.  13. Added the -T and -TM options to pcretest.
673    
674  14. The code in pcre_compile.c for creating the table of named capturing groups  14. The code in pcre_compile.c for creating the table of named capturing groups
675      has been refactored. Instead of creating the table dynamically during the      has been refactored. Instead of creating the table dynamically during the
676      actual compiling pass, the information is remembered during the pre-compile      actual compiling pass, the information is remembered during the pre-compile
677      pass (on the stack unless there are more than 20 named groups, in which      pass (on the stack unless there are more than 20 named groups, in which
678      case malloc() is used) and the whole table is created before the actual      case malloc() is used) and the whole table is created before the actual
679      compile happens. This has simplified the code (it is now nearly 150 lines      compile happens. This has simplified the code (it is now nearly 150 lines
680      shorter) and prepared the way for better handling of references to groups      shorter) and prepared the way for better handling of references to groups
681      with duplicate names.      with duplicate names.
682    
683  15. A back reference to a named subpattern when there is more than one of the  15. A back reference to a named subpattern when there is more than one of the
684      same name now checks them in the order in which they appear in the pattern.      same name now checks them in the order in which they appear in the pattern.
685      The first one that is set is used for the reference. Previously only the      The first one that is set is used for the reference. Previously only the
686      first one was inspected. This change makes PCRE more compatible with Perl.      first one was inspected. This change makes PCRE more compatible with Perl.
687    
688  16. Unicode character properties were updated from Unicode 6.3.0.  16. Unicode character properties were updated from Unicode 6.3.0.
689    
690  17. The compile-time code for auto-possessification has been refactored, based  17. The compile-time code for auto-possessification has been refactored, based
691      on a patch by Zoltan Herczeg. It now happens after instead of during      on a patch by Zoltan Herczeg. It now happens after instead of during
692      compilation. The code is cleaner, and more cases are handled. The option      compilation. The code is cleaner, and more cases are handled. The option
693      PCRE_NO_AUTO_POSSESSIFY is added for testing purposes, and the -O and /O      PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
694      options in pcretest are provided to set it.      options in pcretest are provided to set it. It can also be set by
695        (*NO_AUTO_POSSESS) at the start of a pattern.
696  18. The character VT has been added to the set of characters that match \s and  
697      are generally treated as white space, following this same change in Perl  18. The character VT has been added to the default ("C" locale) set of
698      5.18. There is now no difference between "Perl space" and "POSIX space".      characters that match \s and are generally treated as white space,
699        following this same change in Perl 5.18. There is now no difference between
700  19. The code for checking named groups as conditions, either for being set or      "Perl space" and "POSIX space". Whether VT is treated as white space in
701        other locales depends on the locale.
702    
703    19. The code for checking named groups as conditions, either for being set or
704      for being recursed, has been refactored (this is related to 14 and 15      for being recursed, has been refactored (this is related to 14 and 15
705      above). Processing unduplicated named groups should now be as fast at      above). Processing unduplicated named groups should now be as fast at
706      numerical groups, and processing duplicated groups should be faster than      numerical groups, and processing duplicated groups should be faster than
707      before.      before.
708    
709  20. Two patches to the CMake build system, by Alexander Barkov:  20. Two patches to the CMake build system, by Alexander Barkov:
710    
711        (1) Replace the "source" command by "." in CMakeLists.txt because        (1) Replace the "source" command by "." in CMakeLists.txt because
712            "source" is a bash-ism.            "source" is a bash-ism.
713    
714        (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;        (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
715            without these the CMake build does not work on Solaris.            without these the CMake build does not work on Solaris.
716    
717  21. Perl has changed its handling of \8 and \9. If there is no previously  21. Perl has changed its handling of \8 and \9. If there is no previously
718      encountered capturing group of those numbers, they are treated as the      encountered capturing group of those numbers, they are treated as the
719      literal characters 8 and 9 instead of a binary zero followed by the      literal characters 8 and 9 instead of a binary zero followed by the
720      literals. PCRE now does the same.      literals. PCRE now does the same.
721    
722  22. Following Perl, added \o{} to specify codepoints in octal, making it  22. Following Perl, added \o{} to specify codepoints in octal, making it
723      possible to specify values greater than 0777 and also making them      possible to specify values greater than 0777 and also making them
724      unambiguous.      unambiguous.
725    
726  23. Perl now gives an error for missing closing braces after \x{... instead of  23. Perl now gives an error for missing closing braces after \x{... instead of
727      treating the string as literal. PCRE now does the same.      treating the string as literal. PCRE now does the same.
728    
729  24. RunTest used to grumble if an inappropriate test was selected explicitly,  24. RunTest used to grumble if an inappropriate test was selected explicitly,
730      but just skip it when running all tests. This make it awkward to run ranges      but just skip it when running all tests. This make it awkward to run ranges
731      of tests when one of them was inappropriate. Now it just skips any      of tests when one of them was inappropriate. Now it just skips any
732      inappropriate tests, as it always did when running all tests.      inappropriate tests, as it always did when running all tests.
733    
734  25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained  25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
735      character types such as \d or \w, too many callouts were inserted, and the      character types such as \d or \w, too many callouts were inserted, and the
736      data that they returned was rubbish.      data that they returned was rubbish.
737    
738  26. In UCP mode, \s was not matching two of the characters that Perl matches,  26. In UCP mode, \s was not matching two of the characters that Perl matches,
739      namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they      namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
740      were matched by \h. The code has now been refactored so that the lists of      were matched by \h. The code has now been refactored so that the lists of
741      the horizontal and vertical whitespace characters used for \h and \v (which      the horizontal and vertical whitespace characters used for \h and \v (which
742      are defined only in one place) are now also used for \s.      are defined only in one place) are now also used for \s.
743    
744  27. Add JIT support for the 64 bit TileGX architecture.  27. Add JIT support for the 64 bit TileGX architecture.
745      Patch by Jiong Wang (Tilera Corporation).      Patch by Jiong Wang (Tilera Corporation).
746    
747  28. Possessive quantifiers for classes (both explicit and automatically  28. Possessive quantifiers for classes (both explicit and automatically
748      generated) now use special opcodes instead of wrapping in ONCE brackets.      generated) now use special opcodes instead of wrapping in ONCE brackets.
749    
750  29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier  29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
751      (because it's meaningless), this was not happening when PCRE_CASELESS was      (because it's meaningless), this was not happening when PCRE_CASELESS was
752      set. Not wrong, but inefficient.      set. Not wrong, but inefficient.
753    
754  30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode  30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
755      properties for \w, \d, etc) is present in a test regex. Otherwise if the      properties for \w, \d, etc) is present in a test regex. Otherwise if the
756      test contains no characters greater than 255, Perl doesn't realise it      test contains no characters greater than 255, Perl doesn't realise it
757      should be using Unicode semantics.      should be using Unicode semantics.
758    
759  31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and  31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
760      [:punct:] when PCRE_UCP is set so as to include the same characters as Perl      [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
761      does in Unicode mode.      does in Unicode mode.
762    
763  32. Added the "forbid" facility to pcretest so that putting tests into the  32. Added the "forbid" facility to pcretest so that putting tests into the
764      wrong test files can sometimes be quickly detected.      wrong test files can sometimes be quickly detected.
765    
766  33. There is now a limit (default 250) on the depth of nesting of parentheses.  33. There is now a limit (default 250) on the depth of nesting of parentheses.
767      This limit is imposed to control the amount of system stack used at compile      This limit is imposed to control the amount of system stack used at compile
768      time. It can be changed at build time by --with-parens-nest-limit=xxx or      time. It can be changed at build time by --with-parens-nest-limit=xxx or
769      the equivalent in CMake.      the equivalent in CMake.
770    
771  34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time  34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
772      errors. Perl warns for these when in warning mode, but PCRE has no facility      errors. Perl warns for these when in warning mode, but PCRE has no facility
773      for giving warnings.      for giving warnings.
774    
775  35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.  35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
776      However, this was not working for (?!) because it is optimized to (*FAIL),      However, this was not working for (?!) because it is optimized to (*FAIL),
777      for which PCRE does not allow quantifiers. The optimization is now disabled      for which PCRE does not allow quantifiers. The optimization is now disabled
778      when a quantifier follows (?!). I can't see any use for this, but it makes      when a quantifier follows (?!). I can't see any use for this, but it makes
779      things uniform.      things uniform.
780    
781  36. Perl no longer allows group names to start with digits, so I have made this  36. Perl no longer allows group names to start with digits, so I have made this
782      change also in PCRE. It simplifies the code a bit.      change also in PCRE. It simplifies the code a bit.
783    
784    37. In extended mode, Perl ignores spaces before a + that indicates a
785        possessive quantifier. PCRE allowed a space before the quantifier, but not
786        before the possessive +. It now does.
787    
788    38. The use of \K (reset reported match start) within a repeated possessive
789        group such as (a\Kb)*+ was not working.
790    
791    40. Document that the same character tables must be used at compile time and
792        run time, and that the facility to pass tables to pcre_exec() and
793        pcre_dfa_exec() is for use only with saved/restored patterns.
794    
795    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
796        features for Builds with MSVC:
797    
798        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
799           builds). The .rc files can be used to set FileDescription and many other
800           attributes.
801    
802        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
803           This allows higher-level build scripts which want .pdb files to avoid
804           hard-coding the exact files needed."
805    
806    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
807        mean "start of word" and "end of word", respectively, as a transition aid.
808    
809    43. A minimizing repeat of a class containing codepoints greater than 255 in
810        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
811        compiled to use the heap for recursion.
812    
813    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
814        is configured.
815    
816    
817  Version 8.33 28-May-2013  Version 8.33 28-May-2013

Legend:
Removed from v.1394  
changed lines
  Added in v.1623

  ViewVC Help
Powered by ViewVC 1.1.5