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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.1033  
changed lines
  Added in v.1475

  ViewVC Help
Powered by ViewVC 1.1.5