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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.751  
changed lines
  Added in v.1439

  ViewVC Help
Powered by ViewVC 1.1.5