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

Diff of /code/trunk/ChangeLog

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.5