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

Diff of /code/trunk/ChangeLog

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

revision 1041 by ph10, Sun Sep 16 10:16:27 2012 UTC revision 1514 by ph10, Tue Feb 3 14:34:44 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.32  Version 8.37 xx-xxx-201x
5  ------------  ------------------------
6    
7    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
8        for those parentheses to be closed with whatever has been captured so far.
9        However, it was failing to mark any other groups between the hightest
10        capture so far and the currrent group as "unset". Thus, the ovector for
11        those groups contained whatever was previously there. An example is the
12        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
13    
14    2.  If an assertion condition was quantified with a minimum of zero (an odd
15        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
16    
17    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
18        unrecognized modifier, a crash could occur.
19    
20    
21    
22    Version 8.36 26-September-2014
23    ------------------------------
24    
25    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
26        -Wmissing-field-initializers and -Wunused-parameter.
27    
28    2.  The tests for quantifiers being too big (greater than 65535) were being
29        applied after reading the number, and stupidly assuming that integer
30        overflow would give a negative number. The tests are now applied as the
31        numbers are read.
32    
33    3.  Tidy code in pcre_exec.c where two branches that used to be different are
34        now the same.
35    
36    4.  The JIT compiler did not generate match limit checks for certain
37        bracketed expressions with quantifiers. This may lead to exponential
38        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
39        issue should be resolved now.
40    
41    5.  Fixed an issue, which occures when nested alternatives are optimized
42        with table jumps.
43    
44    6.  Inserted two casts and changed some ints to size_t in the light of some
45        reported 64-bit compiler warnings (Bugzilla 1477).
46    
47    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
48        an empty string, which sometimes were behaving incorrectly in the
49        interpreter (though correctly in the JIT matcher). This pcretest input is
50        an example:
51    
52          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
53          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
54    
55        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
56        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
57        for an empty string was breaking the inner loop and carrying on at a lower
58        level, when possessive repeated groups should always return to a higher
59        level as they have no backtrack points in them. The empty string test now
60        occurs at the outer level.
61    
62    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
63        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
64    
65    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
66        doesn't).
67    
68    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
69        to hold a pattern to be incorrectly computed (too small) when there were
70        named back references to duplicated names. This could cause "internal
71        error: code overflow" or "double free or corruption" or other memory
72        handling errors.
73    
74    11. When named subpatterns had the same prefixes, back references could be
75        confused. For example, in this pattern:
76    
77          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
78    
79        the reference to 'Name' was incorrectly treated as a reference to a
80        duplicate name.
81    
82    12. A pattern such as /^s?c/mi8 where the optional character has more than
83        one "other case" was incorrectly compiled such that it would only try to
84        match starting at "c".
85    
86    13. When a pattern starting with \s was studied, VT was not included in the
87        list of possible starting characters; this should have been part of the
88        8.34/18 patch.
89    
90    14. If a character class started [\Qx]... where x is any character, the class
91        was incorrectly terminated at the ].
92    
93    15. If a pattern that started with a caseless match for a character with more
94        than one "other case" was studied, PCRE did not set up the starting code
95        unit bit map for the list of possible characters. Now it does. This is an
96        optimization improvement, not a bug fix.
97    
98    16. The Unicode data tables have been updated to Unicode 7.0.0.
99    
100    17. Fixed a number of memory leaks in pcregrep.
101    
102    18. Avoid a compiler warning (from some compilers) for a function call with
103        a cast that removes "const" from an lvalue by using an intermediate
104        variable (to which the compiler does not object).
105    
106    19. Incorrect code was compiled if a group that contained an internal recursive
107        back reference was optional (had quantifier with a minimum of zero). This
108        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
109        caused segmentation faults because of stack overflows at compile time.
110    
111    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
112        group that is quantified with an indefinite repeat, caused a compile-time
113        loop which used up all the system stack and provoked a segmentation fault.
114        This was not the same bug as 19 above.
115    
116    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
117        Patch by Mike Frysinger.
118    
119    
120    Version 8.35 04-April-2014
121    --------------------------
122    
123    1.  A new flag is set, when property checks are present in an XCLASS.
124        When this flag is not set, PCRE can perform certain optimizations
125        such as studying these XCLASS-es.
126    
127    2.  The auto-possessification of character sets were improved: a normal
128        and an extended character set can be compared now. Furthermore
129        the JIT compiler optimizes more character set checks.
130    
131    3.  Got rid of some compiler warnings for potentially uninitialized variables
132        that show up only when compiled with -O2.
133    
134    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
135        of a match later then the end of the match. The pcretest program was not
136        handling the case sensibly - it was outputting from the start to the next
137        binary zero. It now reports this situation in a message, and outputs the
138        text from the end to the start.
139    
140    5.  Fast forward search is improved in JIT. Instead of the first three
141        characters, any three characters with fixed position can be searched.
142        Search order: first, last, middle.
143    
144    6.  Improve character range checks in JIT. Characters are read by an inprecise
145        function now, which returns with an unknown value if the character code is
146        above a certain threshold (e.g: 256). The only limitation is that the value
147        must be bigger than the threshold as well. This function is useful when
148        the characters above the threshold are handled in the same way.
149    
150    7.  The macros whose names start with RAWUCHAR are placeholders for a future
151        mode in which only the bottom 21 bits of 32-bit data items are used. To
152        make this more memorable for those maintaining the code, the names have
153        been changed to start with UCHAR21, and an extensive comment has been added
154        to their definition.
155    
156    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
157        to the export list in Makefile.am (they were accidentally omitted from the
158        8.34 tarball).
159    
160    9.  The informational output from pcretest used the phrase "starting byte set"
161        which is inappropriate for the 16-bit and 32-bit libraries. As the output
162        for "first char" and "need char" really means "non-UTF-char", I've changed
163        "byte" to "char", and slightly reworded the output. The documentation about
164        these values has also been (I hope) clarified.
165    
166    10. Another JIT related optimization: use table jumps for selecting the correct
167        backtracking path, when more than four alternatives are present inside a
168        bracket.
169    
170    11. Empty match is not possible, when the minimum length is greater than zero,
171        and there is no \K in the pattern. JIT should avoid empty match checks in
172        such cases.
173    
174    12. In a caseless character class with UCP support, when a character with more
175        than one alternative case was not the first character of a range, not all
176        the alternative cases were added to the class. For example, s and \x{17f}
177        are both alternative cases for S: the class [RST] was handled correctly,
178        but [R-T] was not.
179    
180    13. The configure.ac file always checked for pthread support when JIT was
181        enabled. This is not used in Windows, so I have put this test inside a
182        check for the presence of windows.h (which was already tested for).
183    
184    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
185        The algorithm provides a way to skip certain starting offsets, and usually
186        faster than linear prefix searches.
187    
188    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
189        as for 'fr_FR' and 'french'. For some reason, however, it then used the
190        Windows-specific input and output files, which have 'french' screwed in.
191        So this could never have worked. One of the problems with locales is that
192        they aren't always the same. I have now updated RunTest so that it checks
193        the output of the locale test (test 3) against three different output
194        files, and it allows the test to pass if any one of them matches. With luck
195        this should make the test pass on some versions of Solaris where it was
196        failing. Because of the uncertainty, the script did not used to stop if
197        test 3 failed; it now does. If further versions of a French locale ever
198        come to light, they can now easily be added.
199    
200    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
201        there was a message during ./configure, but it did not stop. This now
202        provokes an error. The invalid example in README has been corrected.
203        If a value less than the minimum is given, the minimum value has always
204        been used, but now a warning is given.
205    
206    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
207        was a bug in the test system, which is now fixed. Also, the list of various
208        configurations that are tested for each release did not have one with both
209        16/32 bits and --enable-bar-anycrlf. It now does.
210    
211    18. pcretest was missing "-C bsr" for displaying the \R default setting.
212    
213    19. Little endian PowerPC systems are supported now by the JIT compiler.
214    
215    20. The fast forward newline mechanism could enter to an infinite loop on
216        certain invalid UTF-8 input. Although we don't support these cases
217        this issue can be fixed by a performance optimization.
218    
219    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
220        not take account if existing stack usage. There is now a new global
221        variable called pcre_stack_guard that can be set to point to an external
222        function to check stack availability. It is called at the start of
223        processing every parenthesized group.
224    
225    22. A typo in the code meant that in ungreedy mode the max/min qualifier
226        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
227        not match "ab".
228    
229    23. When UTF was disabled, the JIT program reported some incorrect compile
230        errors. These messages are silenced now.
231    
232    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
233        compiler.
234    
235    25. Change all the temporary files used in RunGrepTest to be different to those
236        used by RunTest so that the tests can be run simultaneously, for example by
237        "make -j check".
238    
239    
240    Version 8.34 15-December-2013
241    -----------------------------
242    
243    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
244        executable memory. Patch inspired by Carsten Klein.
245    
246    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
247        this macro is never tested and has no effect, because the work to support
248        coverage involves only compiling and linking options and special targets in
249        the Makefile. The comment in config.h implied that defining the macro would
250        enable coverage support, which is totally false. There was also support for
251        setting this macro in the CMake files (my fault, I just copied it from
252        configure). SUPPORT_GCOV has now been removed.
253    
254    3.  Make a small performance improvement in strlen16() and strlen32() in
255        pcretest.
256    
257    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
258        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
259        these cases). There was also one in pcretest.c.
260    
261    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
262    
263    6.  In UTF mode, the code for checking whether a group could match an empty
264        string (which is used for indefinitely repeated groups to allow for
265        breaking an infinite loop) was broken when the group contained a repeated
266        negated single-character class with a character that occupied more than one
267        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
268        UTF-8 mode). The effect was undefined: the group might or might not be
269        deemed as matching an empty string, or the program might have crashed.
270    
271    7.  The code for checking whether a group could match an empty string was not
272        recognizing that \h, \H, \v, \V, and \R must match a character.
273    
274    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
275        an empty string. If it can, pcretest shows this in its information output.
276    
277    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
278        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
279        matched by pcre_exec() without using JIT:
280    
281        (a) If the rest of the pattern did not match after a maximal run of
282            grapheme clusters, the code for backing up to try with fewer of them
283            did not always back up over a full grapheme when characters that do not
284            have the modifier quality were involved, e.g. Hangul syllables.
285    
286        (b) If the match point in a subject started with modifier character, and
287            there was no match, the code could incorrectly back up beyond the match
288            point, and potentially beyond the first character in the subject,
289            leading to a segfault or an incorrect match result.
290    
291    10. A conditional group with an assertion condition could lead to PCRE
292        recording an incorrect first data item for a match if no other first data
293        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
294        first data item, and therefore matched "ca" after "c" instead of at the
295        start.
296    
297    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
298        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
299    
300    12. The source of pcregrep now includes z/OS-specific code so that it can be
301        compiled for z/OS as part of the special z/OS distribution.
302    
303    13. Added the -T and -TM options to pcretest.
304    
305    14. The code in pcre_compile.c for creating the table of named capturing groups
306        has been refactored. Instead of creating the table dynamically during the
307        actual compiling pass, the information is remembered during the pre-compile
308        pass (on the stack unless there are more than 20 named groups, in which
309        case malloc() is used) and the whole table is created before the actual
310        compile happens. This has simplified the code (it is now nearly 150 lines
311        shorter) and prepared the way for better handling of references to groups
312        with duplicate names.
313    
314    15. A back reference to a named subpattern when there is more than one of the
315        same name now checks them in the order in which they appear in the pattern.
316        The first one that is set is used for the reference. Previously only the
317        first one was inspected. This change makes PCRE more compatible with Perl.
318    
319    16. Unicode character properties were updated from Unicode 6.3.0.
320    
321    17. The compile-time code for auto-possessification has been refactored, based
322        on a patch by Zoltan Herczeg. It now happens after instead of during
323        compilation. The code is cleaner, and more cases are handled. The option
324        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
325        options in pcretest are provided to set it. It can also be set by
326        (*NO_AUTO_POSSESS) at the start of a pattern.
327    
328    18. The character VT has been added to the default ("C" locale) set of
329        characters that match \s and are generally treated as white space,
330        following this same change in Perl 5.18. There is now no difference between
331        "Perl space" and "POSIX space". Whether VT is treated as white space in
332        other locales depends on the locale.
333    
334    19. The code for checking named groups as conditions, either for being set or
335        for being recursed, has been refactored (this is related to 14 and 15
336        above). Processing unduplicated named groups should now be as fast at
337        numerical groups, and processing duplicated groups should be faster than
338        before.
339    
340    20. Two patches to the CMake build system, by Alexander Barkov:
341    
342          (1) Replace the "source" command by "." in CMakeLists.txt because
343              "source" is a bash-ism.
344    
345          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
346              without these the CMake build does not work on Solaris.
347    
348    21. Perl has changed its handling of \8 and \9. If there is no previously
349        encountered capturing group of those numbers, they are treated as the
350        literal characters 8 and 9 instead of a binary zero followed by the
351        literals. PCRE now does the same.
352    
353    22. Following Perl, added \o{} to specify codepoints in octal, making it
354        possible to specify values greater than 0777 and also making them
355        unambiguous.
356    
357    23. Perl now gives an error for missing closing braces after \x{... instead of
358        treating the string as literal. PCRE now does the same.
359    
360    24. RunTest used to grumble if an inappropriate test was selected explicitly,
361        but just skip it when running all tests. This make it awkward to run ranges
362        of tests when one of them was inappropriate. Now it just skips any
363        inappropriate tests, as it always did when running all tests.
364    
365    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
366        character types such as \d or \w, too many callouts were inserted, and the
367        data that they returned was rubbish.
368    
369    26. In UCP mode, \s was not matching two of the characters that Perl matches,
370        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
371        were matched by \h. The code has now been refactored so that the lists of
372        the horizontal and vertical whitespace characters used for \h and \v (which
373        are defined only in one place) are now also used for \s.
374    
375    27. Add JIT support for the 64 bit TileGX architecture.
376        Patch by Jiong Wang (Tilera Corporation).
377    
378    28. Possessive quantifiers for classes (both explicit and automatically
379        generated) now use special opcodes instead of wrapping in ONCE brackets.
380    
381    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
382        (because it's meaningless), this was not happening when PCRE_CASELESS was
383        set. Not wrong, but inefficient.
384    
385    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
386        properties for \w, \d, etc) is present in a test regex. Otherwise if the
387        test contains no characters greater than 255, Perl doesn't realise it
388        should be using Unicode semantics.
389    
390    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
391        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
392        does in Unicode mode.
393    
394    32. Added the "forbid" facility to pcretest so that putting tests into the
395        wrong test files can sometimes be quickly detected.
396    
397    33. There is now a limit (default 250) on the depth of nesting of parentheses.
398        This limit is imposed to control the amount of system stack used at compile
399        time. It can be changed at build time by --with-parens-nest-limit=xxx or
400        the equivalent in CMake.
401    
402    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
403        errors. Perl warns for these when in warning mode, but PCRE has no facility
404        for giving warnings.
405    
406    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
407        However, this was not working for (?!) because it is optimized to (*FAIL),
408        for which PCRE does not allow quantifiers. The optimization is now disabled
409        when a quantifier follows (?!). I can't see any use for this, but it makes
410        things uniform.
411    
412    36. Perl no longer allows group names to start with digits, so I have made this
413        change also in PCRE. It simplifies the code a bit.
414    
415    37. In extended mode, Perl ignores spaces before a + that indicates a
416        possessive quantifier. PCRE allowed a space before the quantifier, but not
417        before the possessive +. It now does.
418    
419    38. The use of \K (reset reported match start) within a repeated possessive
420        group such as (a\Kb)*+ was not working.
421    
422    40. Document that the same character tables must be used at compile time and
423        run time, and that the facility to pass tables to pcre_exec() and
424        pcre_dfa_exec() is for use only with saved/restored patterns.
425    
426    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
427        features for Builds with MSVC:
428    
429        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
430           builds). The .rc files can be used to set FileDescription and many other
431           attributes.
432    
433        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
434           This allows higher-level build scripts which want .pdb files to avoid
435           hard-coding the exact files needed."
436    
437    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
438        mean "start of word" and "end of word", respectively, as a transition aid.
439    
440    43. A minimizing repeat of a class containing codepoints greater than 255 in
441        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
442        compiled to use the heap for recursion.
443    
444    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
445        is configured.
446    
447    
448    Version 8.33 28-May-2013
449    ------------------------
450    
451    1.  Added 'U' to some constants that are compared to unsigned integers, to
452        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
453        variables that are added to signed variables, to ensure the result is
454        signed and can be negated.
455    
456    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
457        CMake config files.
458    
459    3.  Revise the creation of config.h.generic so that all boolean macros are
460        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
461        overriding via -D on the command line possible.
462    
463    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
464        to unsigned int is reported to make a quite noticeable speed difference in
465        a specific Windows environment. Testing on Linux did also appear to show
466        some benefit (and it is clearly not harmful). Also fixed the definition of
467        Xop which should be unsigned.
468    
469    5.  Related to (4), changing the definition of the intermediate variable cc
470        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
471        improvements.
472    
473    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
474        unnecessary spaces.
475    
476    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
477        and later.
478    
479    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
480    
481    9.  Optimizing fast_forward_start_bits in JIT.
482    
483    10. Adding support for callouts in JIT, and fixing some issues revealed
484        during this work. Namely:
485    
486        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
487    
488        (b) Minimum length was not checked before the matching is started.
489    
490    11. The value of capture_last that is passed to callouts was incorrect in some
491        cases when there was a capture on one path that was subsequently abandoned
492        after a backtrack. Also, the capture_last value is now reset after a
493        recursion, since all captures are also reset in this case.
494    
495    12. The interpreter no longer returns the "too many substrings" error in the
496        case when an overflowing capture is in a branch that is subsequently
497        abandoned after a backtrack.
498    
499    13. In the pathological case when an offset vector of size 2 is used, pcretest
500        now prints out the matched string after a yield of 0 or 1.
501    
502    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
503        Only supported by the JIT compiler at the moment.
504    
505    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
506    
507    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
508        offset of the starting point of the matching process, provided the offsets
509        vector is large enough.
510    
511    17. The \A escape now records a lookbehind value of 1, though its execution
512        does not actually inspect the previous character. This is to ensure that,
513        in partial multi-segment matching, at least one character from the old
514        segment is retained when a new segment is processed. Otherwise, if there
515        are no lookbehinds in the pattern, \A might match incorrectly at the start
516        of a new segment.
517    
518    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
519    
520    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
521        gives some modest performance improvement in 8-bit mode.
522    
523    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
524        be expressed in certain programming languages using Universal Character
525        Names.
526    
527    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
528        which points out that "non characters" are not "characters that may not
529        appear in Unicode strings" but rather "characters that are reserved for
530        internal use and have only local meaning".
531    
532    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
533        there was a conditional group that depended on an assertion, if the
534        assertion was false, the callout that immediately followed the alternation
535        in the condition was skipped when pcre_exec() was used for matching.
536    
537    23. Allow an explicit callout to be inserted before an assertion that is the
538        condition for a conditional group, for compatibility with automatic
539        callouts, which always insert a callout at this point.
540    
541    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
542        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
543    
544    25. (*PRUNE) is now supported by the JIT compiler.
545    
546    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
547    
548    27. Fix the case where there are two or more SKIPs with arguments that may be
549        ignored.
550    
551    28. (*SKIP) is now supported by the JIT compiler.
552    
553    29. (*THEN) is now supported by the JIT compiler.
554    
555    30. Update RunTest with additional test selector options.
556    
557    31. The way PCRE handles backtracking verbs has been changed in two ways.
558    
559        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
560        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
561        backtracking. In some cases this makes it more Perl-compatible, but Perl's
562        rather obscure rules do not always do the same thing.
563    
564        (2) Previously, backtracking verbs were confined within assertions. This is
565        no longer the case for positive assertions, except for (*ACCEPT). Again,
566        this sometimes improves Perl compatibility, and sometimes does not.
567    
568    32. A number of tests that were in test 2 because Perl did things differently
569        have been moved to test 1, because either Perl or PCRE has changed, and
570        these tests are now compatible.
571    
572    32. Backtracking control verbs are now handled in the same way in JIT and
573        interpreter.
574    
575    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
576        contained a forward subroutine reference caused a compile error.
577    
578    34. Auto-detect and optimize limited repetitions in JIT.
579    
580    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
581        blocking (*UTF) etc.
582    
583    36. In the interpreter, maximizing pattern repetitions for characters and
584        character types now use tail recursion, which reduces stack usage.
585    
586    37. The value of the max lookbehind was not correctly preserved if a compiled
587        and saved regex was reloaded on a host of different endianness.
588    
589    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
590        of the compiled pattern block, expand the flags field from 16 to 32 bits
591        because it was almost full.
592    
593    39. Try madvise first before posix_madvise.
594    
595    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
596        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
597        original change locked out all matches of empty strings. This has been
598        changed so that one match of an empty string per line is recognized.
599        Subsequent searches on the same line (for colouring or for --only-matching,
600        for example) do not recognize empty strings.
601    
602    41. Applied a user patch to fix a number of spelling mistakes in comments.
603    
604    42. Data lines longer than 65536 caused pcretest to crash.
605    
606    43. Clarified the data type for length and startoffset arguments for pcre_exec
607        and pcre_dfa_exec in the function-specific man pages, where they were
608        explicitly stated to be in bytes, never having been updated. I also added
609        some clarification to the pcreapi man page.
610    
611    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
612        a segmentation fault.
613    
614    
615    Version 8.32 30-November-2012
616    -----------------------------
617    
618  1.  Improved JIT compiler optimizations for first character search and single  1.  Improved JIT compiler optimizations for first character search and single
619      character iterators.      character iterators.
# Line 16  Version 8.32 Line 627  Version 8.32
627    
628  5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.  5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
629      Reported by Giuseppe D'Angelo.      Reported by Giuseppe D'Angelo.
630    
631  6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start  6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
632      of a line, was being set incorrectly in cases where .* appeared inside      of a line, was being set incorrectly in cases where .* appeared inside
633      atomic brackets at the start of a pattern, or where there was a subsequent      atomic brackets at the start of a pattern, or where there was a subsequent
634      *PRUNE or *SKIP.      *PRUNE or *SKIP.
635    
636  7.  Improved instruction cache flush for POWER/PowerPC.  7.  Improved instruction cache flush for POWER/PowerPC.
637      Patch by Daniel Richard G.      Patch by Daniel Richard G.
638    
639  8.  Fixed a number of issues in pcregrep, making it more compatible with GNU  8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
640      grep:      grep:
641    
642      (a) There is now no limit to the number of patterns to be matched.      (a) There is now no limit to the number of patterns to be matched.
643    
644      (b) An error is given if a pattern is too long.      (b) An error is given if a pattern is too long.
645    
646      (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir      (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
647          are now supported.          are now supported.
648    
649      (d) --exclude-from and --include-from (multiple use) have been added.      (d) --exclude-from and --include-from (multiple use) have been added.
650    
651      (e) Exclusions and inclusions now apply to all files and directories, not      (e) Exclusions and inclusions now apply to all files and directories, not
652          just to those obtained from scanning a directory recursively.          just to those obtained from scanning a directory recursively.
653    
654      (f) Multiple uses of -f and --file-list are now supported.      (f) Multiple uses of -f and --file-list are now supported.
655    
656      (g) In a Windows environment, the default for -d has been changed from      (g) In a Windows environment, the default for -d has been changed from
657          "read" (the GNU grep default) to "skip", because otherwise the presence          "read" (the GNU grep default) to "skip", because otherwise the presence
658          of a directory in the file list provokes an error.          of a directory in the file list provokes an error.
659    
660      (h) The documentation has been revised and clarified in places.      (h) The documentation has been revised and clarified in places.
661    
662  9.  Improve the matching speed of capturing brackets.  9.  Improve the matching speed of capturing brackets.
663    
664  10. Changed the meaning of \X so that it now matches a Unicode extended  10. Changed the meaning of \X so that it now matches a Unicode extended
665      grapheme cluster.      grapheme cluster.
666    
667  11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting  11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
668      out POSIX threads when JIT support is configured.      out POSIX threads when JIT support is configured.
669    
670  12. Added support for PCRE_STUDY_EXTRA_NEEDED.  12. Added support for PCRE_STUDY_EXTRA_NEEDED.
671    
672  13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg  13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
673      structure could go wrong in environments where size_t is not the same size      structure could go wrong in environments where size_t is not the same size
674      as int.      as int.
675    
676  14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be  14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
677      set.      set.
678    
679  15. The EBCDIC support had decayed; later updates to the code had included  15. The EBCDIC support had decayed; later updates to the code had included
680      explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a      explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
681      general tidy up of EBCDIC-related issues, and the documentation was also      general tidy up of EBCDIC-related issues, and the documentation was also
682      not quite right. There is now a test that can be run on ASCII systems to      not quite right. There is now a test that can be run on ASCII systems to
683      check some of the EBCDIC-related things (but is it not a full test).      check some of the EBCDIC-related things (but is it not a full test).
684    
685  16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting  16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
686      in a small tidy to the code.      in a small tidy to the code.
687    
688  17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.  17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
689    
690  18. If the --only-matching (-o) option in pcregrep is specified multiple  18. If the --only-matching (-o) option in pcregrep is specified multiple
691      times, each one causes appropriate output. For example, -o1 -o2 outputs the      times, each one causes appropriate output. For example, -o1 -o2 outputs the
692      substrings matched by the 1st and 2nd capturing parentheses. A separating      substrings matched by the 1st and 2nd capturing parentheses. A separating
693      string can be specified by --om-separator (default empty).      string can be specified by --om-separator (default empty).
694    
695  19. Improving the first n character searches.  19. Improving the first n character searches.
696    
697  20. Turn case lists for horizontal and vertical white space into macros so that  20. Turn case lists for horizontal and vertical white space into macros so that
698      they are defined only once.      they are defined only once.
699    
700    21. This set of changes together give more compatible Unicode case-folding
701        behaviour for characters that have more than one other case when UCP
702        support is available.
703    
704        (a) The Unicode property table now has offsets into a new table of sets of
705            three or more characters that are case-equivalent. The MultiStage2.py
706            script that generates these tables (the pcre_ucd.c file) now scans
707            CaseFolding.txt instead of UnicodeData.txt for character case
708            information.
709    
710        (b) The code for adding characters or ranges of characters to a character
711            class has been abstracted into a generalized function that also handles
712            case-independence. In UTF-mode with UCP support, this uses the new data
713            to handle characters with more than one other case.
714    
715        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
716            whose other case is greater than 256 are now correctly matched
717            caselessly. Previously, the high codepoint matched the low one, but not
718            vice versa.
719    
720        (d) The processing of \h, \H, \v, and \ in character classes now makes use
721            of the new class addition function, using character lists defined as
722            macros alongside the case definitions of 20 above.
723    
724        (e) Caseless back references now work with characters that have more than
725            one other case.
726    
727        (f) General caseless matching of characters with more than one other case
728            is supported.
729    
730    22. Unicode character properties were updated from Unicode 6.2.0
731    
732    23. Improved CMake support under Windows. Patch by Daniel Richard G.
733    
734    24. Add support for 32-bit character strings, and UTF-32
735    
736    25. Major JIT compiler update (code refactoring and bugfixing).
737        Experimental Sparc 32 support is added.
738    
739    26. Applied a modified version of Daniel Richard G's patch to create
740        pcre.h.generic and config.h.generic by "make" instead of in the
741        PrepareRelease script.
742    
743    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
744        pcre_compile.c when checking for a zero character.
745    
746    28. Introducing a native interface for JIT. Through this interface, the compiled
747        machine code can be directly executed. The purpose of this interface is to
748        provide fast pattern matching, so several sanity checks are not performed.
749        However, feature tests are still performed. The new interface provides
750        1.4x speedup compared to the old one.
751    
752    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
753        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
754        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
755    
756    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
757        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
758        the "old" RFC 2279). Instead, it ended up passing a negative length to
759        pcre_exec().
760    
761    31. Add support for GCC's visibility feature to hide internal functions.
762    
763    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
764        "unknown -C option" after outputting 0 or 1.
765    
766    33. There is now support for generating a code coverage report for the test
767        suite in environments where gcc is the compiler and lcov is installed. This
768        is mainly for the benefit of the developers.
769    
770    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
771        unaddressable using valgrind annotations, allowing valgrind to detect
772        invalid memory accesses. This is mainly for the benefit of the developers.
773    
774    25. (*UTF) can now be used to start a pattern in any of the three libraries.
775    
776    26. Give configure error if --enable-cpp but no C++ compiler found.
777    
778    
779  Version 8.31 06-July-2012  Version 8.31 06-July-2012
780  -------------------------  -------------------------
# Line 1430  Version 7.9 11-Apr-09 Line 2119  Version 7.9 11-Apr-09
2119  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
2120      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
2121      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2122      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2123        8.33.]
2124    
2125  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
2126      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1673  Version 7.7 07-May-08 Line 2363  Version 7.7 07-May-08
2363      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2364      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2365      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2366      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2367      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2368      was subsequently set up correctly.)      was subsequently set up correctly.)
2369    

Legend:
Removed from v.1041  
changed lines
  Added in v.1514

  ViewVC Help
Powered by ViewVC 1.1.5