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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.659  
changed lines
  Added in v.1369

  ViewVC Help
Powered by ViewVC 1.1.5