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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.753  
changed lines
  Added in v.1449

  ViewVC Help
Powered by ViewVC 1.1.5