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

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

  ViewVC Help
Powered by ViewVC 1.1.5