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

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

  ViewVC Help
Powered by ViewVC 1.1.5