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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.752  
changed lines
  Added in v.1477

  ViewVC Help
Powered by ViewVC 1.1.5