/[pcre]/code/trunk/ChangeLog

Diff of /code/trunk/ChangeLog

Parent Directory | Revision Log | View Patch Patch

-revision 773 by ph10,
Wed Nov 30 18:10:27 2011 UTC
+revision 1354 by ph10,
Mon Aug 12 14:31:07 2013 UTC
 Line 1
  ChangeLog for PCRE
  ------------------
- Version 8.21
+ Version 8.34 xx-xxxx-201x
- ------------
+ --------------------------
+.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
+     executable memory. Patch inspired by Carsten Klein.
+.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
+     this macro is never tested and has no effect, because the work to support
+     coverage involves only compiling and linking options and special targets in
+     the Makefile. The comment in config.h implied that defining the macro would
+     enable coverage support, which is totally false. There was also support for
+     setting this macro in the CMake files (my fault, I just copied it from
+     configure). SUPPORT_GCOV has now been removed.
+.  Make a small performance improvement in strlen16() and strlen32() in
+     pcretest.
+.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
+     detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
+     these cases). There was also one in pcretest.c.
+.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
+.  In UTF mode, the code for checking whether a group could match an empty
+     string (which is used for indefinitely repeated groups to allow for
+     breaking an infinite loop) was broken when the group contained a repeated
+     negated single-character class with a character that occupied more than one
+     data item and had a minimum repetition of zero (for example, [^\x{100}]* in
+     UTF-8 mode). The effect was undefined: the group might or might not be
+     deemed as matching an empty string, or the program might have crashed.
+.  The code for checking whether a group could match an empty string was not
+     recognizing that \h, \H, \v, \V, and \R must match a character.
+.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
+     an empty string. If it can, pcretest shows this in its information output.
+.  Fixed two related bugs that applied to Unicode extended grapheme clusters
+     that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
+     matched by pcre_exec() without using JIT:
+     (a) If the rest of the pattern did not match after a maximal run of
+         grapheme clusters, the code for backing up to try with fewer of them
+         did not always back up over a full grapheme when characters that do not
+         have the modifier quality were involved, e.g. Hangul syllables.
+     (b) If the match point in a subject started with modifier character, and
+         there was no match, the code could incorrectly back up beyond the match
+         point, and potentially beyond the first character in the subject,
+         leading to a segfault or an incorrect match result.
+. A conditional group with an assertion condition could lead to PCRE
+     recording an incorrect first data item for a match if no other firse data
+     item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
+     first data item, and therefore matched "ca" after "c" instead of at the
+     start.
+. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
+     bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
+. The source of pcregrep now includes z/OS-specific code so that it can be
+     compiled for z/OS as part of the special z/OS distribution.
+ Version 8.33 28-May-2013
+ ------------------------
+.  Added 'U' to some constants that are compared to unsigned integers, to
+     avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
+     variables that are added to signed variables, to ensure the result is
+     signed and can be negated.
+.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
+     CMake config files.
+.  Revise the creation of config.h.generic so that all boolean macros are
+     #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
+     overriding via -D on the command line possible.
+.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
+     to unsigned int is reported to make a quite noticeable speed difference in
+     a specific Windows environment. Testing on Linux did also appear to show
+     some benefit (and it is clearly not harmful). Also fixed the definition of
+     Xop which should be unsigned.
+.  Related to (4), changing the definition of the intermediate variable cc
+     in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
+     improvements.
+.  Fix forward search in JIT when link size is 3 or greater. Also removed some
+     unnecessary spaces.
+.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
+     and later.
+.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
+.  Optimizing fast_forward_start_bits in JIT.
+. Adding support for callouts in JIT, and fixing some issues revealed
+     during this work. Namely:
+     (a) Unoptimized capturing brackets incorrectly reset on backtrack.
+     (b) Minimum length was not checked before the matching is started.
+. The value of capture_last that is passed to callouts was incorrect in some
+     cases when there was a capture on one path that was subsequently abandoned
+     after a backtrack. Also, the capture_last value is now reset after a
+     recursion, since all captures are also reset in this case.
+. The interpreter no longer returns the "too many substrings" error in the
+     case when an overflowing capture is in a branch that is subsequently
+     abandoned after a backtrack.
+. In the pathological case when an offset vector of size 2 is used, pcretest
+     now prints out the matched string after a yield of 0 or 1.
+. Inlining subpatterns in recursions, when certain conditions are fulfilled.
+     Only supported by the JIT compiler at the moment.
+. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
+. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
+     offset of the starting point of the matching process, provided the offsets
+     vector is large enough.
+. The \A escape now records a lookbehind value of 1, though its execution
+     does not actually inspect the previous character. This is to ensure that,
+     in partial multi-segment matching, at least one character from the old
+     segment is retained when a new segment is processed. Otherwise, if there
+     are no lookbehinds in the pattern, \A might match incorrectly at the start
+     of a new segment.
+. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
+. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
+     gives some modest performance improvement in 8-bit mode.
+. Added the PCRE-specific property \p{Xuc} for matching characters that can
+     be expressed in certain programming languages using Universal Character
+     Names.
+. Unicode validation has been updated in the light of Unicode Corrigendum #9,
+     which points out that "non characters" are not "characters that may not
+     appear in Unicode strings" but rather "characters that are reserved for
+     internal use and have only local meaning".
+. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
+     there was a conditional group that depended on an assertion, if the
+     assertion was false, the callout that immediately followed the alternation
+     in the condition was skipped when pcre_exec() was used for matching.
+. Allow an explicit callout to be inserted before an assertion that is the
+     condition for a conditional group, for compatibility with automatic
+     callouts, which always insert a callout at this point.
+. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
+     confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
+. (*PRUNE) is now supported by the JIT compiler.
+. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
+. Fix the case where there are two or more SKIPs with arguments that may be
+     ignored.
+. (*SKIP) is now supported by the JIT compiler.
+. (*THEN) is now supported by the JIT compiler.
+. Update RunTest with additional test selector options.
+. The way PCRE handles backtracking verbs has been changed in two ways.
+     (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
+     SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
+     backtracking. In some cases this makes it more Perl-compatible, but Perl's
+     rather obscure rules do not always do the same thing.
+     (2) Previously, backtracking verbs were confined within assertions. This is
+     no longer the case for positive assertions, except for (*ACCEPT). Again,
+     this sometimes improves Perl compatibility, and sometimes does not.
+. A number of tests that were in test 2 because Perl did things differently
+     have been moved to test 1, because either Perl or PCRE has changed, and
+     these tests are now compatible.
+. Backtracking control verbs are now handled in the same way in JIT and
+     interpreter.
+. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
+     contained a forward subroutine reference caused a compile error.
+. Auto-detect and optimize limited repetitions in JIT.
+. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
+     blocking (*UTF) etc.
+. In the interpreter, maximizing pattern repetitions for characters and
+     character types now use tail recursion, which reduces stack usage.
+. The value of the max lookbehind was not correctly preserved if a compiled
+     and saved regex was reloaded on a host of different endianness.
+. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
+     of the compiled pattern block, expand the flags field from 16 to 32 bits
+     because it was almost full.
+. Try madvise first before posix_madvise.
+. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
+     with a pattern such as ^$. It has taken 4 years for anybody to notice! The
+     original change locked out all matches of empty strings. This has been
+     changed so that one match of an empty string per line is recognized.
+     Subsequent searches on the same line (for colouring or for --only-matching,
+     for example) do not recognize empty strings.
+. Applied a user patch to fix a number of spelling mistakes in comments.
+. Data lines longer than 65536 caused pcretest to crash.
+. Clarified the data type for length and startoffset arguments for pcre_exec
+     and pcre_dfa_exec in the function-specific man pages, where they were
+     explicitly stated to be in bytes, never having been updated. I also added
+     some clarification to the pcreapi man page.
+. A call to pcre_dfa_exec() with an output vector size less than 2 caused
+     a segmentation fault.
+ Version 8.32 30-November-2012
+ -----------------------------
+.  Improved JIT compiler optimizations for first character search and single
+     character iterators.
+.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
+     Patch by Daniel Richard G.
+.  Single character iterator optimizations in the JIT compiler.
+.  Improved JIT compiler optimizations for character ranges.
+.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
+     Reported by Giuseppe D'Angelo.
+.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
+     of a line, was being set incorrectly in cases where .* appeared inside
+     atomic brackets at the start of a pattern, or where there was a subsequent
+     *PRUNE or *SKIP.
+.  Improved instruction cache flush for POWER/PowerPC.
+     Patch by Daniel Richard G.
+.  Fixed a number of issues in pcregrep, making it more compatible with GNU
+     grep:
+     (a) There is now no limit to the number of patterns to be matched.
+     (b) An error is given if a pattern is too long.
+     (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
+         are now supported.
+     (d) --exclude-from and --include-from (multiple use) have been added.
+     (e) Exclusions and inclusions now apply to all files and directories, not
+         just to those obtained from scanning a directory recursively.
+     (f) Multiple uses of -f and --file-list are now supported.
+     (g) In a Windows environment, the default for -d has been changed from
+         "read" (the GNU grep default) to "skip", because otherwise the presence
+         of a directory in the file list provokes an error.
+     (h) The documentation has been revised and clarified in places.
+.  Improve the matching speed of capturing brackets.
+. Changed the meaning of \X so that it now matches a Unicode extended
+     grapheme cluster.
+. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
+     out POSIX threads when JIT support is configured.
+. Added support for PCRE_STUDY_EXTRA_NEEDED.
+. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
+     structure could go wrong in environments where size_t is not the same size
+     as int.
+. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
+     set.
+. The EBCDIC support had decayed; later updates to the code had included
+     explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
+     general tidy up of EBCDIC-related issues, and the documentation was also
+     not quite right. There is now a test that can be run on ASCII systems to
+     check some of the EBCDIC-related things (but is it not a full test).
+. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
+     in a small tidy to the code.
+. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
+. If the --only-matching (-o) option in pcregrep is specified multiple
+     times, each one causes appropriate output. For example, -o1 -o2 outputs the
+     substrings matched by the 1st and 2nd capturing parentheses. A separating
+     string can be specified by --om-separator (default empty).
+. Improving the first n character searches.
+. Turn case lists for horizontal and vertical white space into macros so that
+     they are defined only once.
+. This set of changes together give more compatible Unicode case-folding
+     behaviour for characters that have more than one other case when UCP
+     support is available.
+     (a) The Unicode property table now has offsets into a new table of sets of
+         three or more characters that are case-equivalent. The MultiStage2.py
+         script that generates these tables (the pcre_ucd.c file) now scans
+         CaseFolding.txt instead of UnicodeData.txt for character case
+         information.
+     (b) The code for adding characters or ranges of characters to a character
+         class has been abstracted into a generalized function that also handles
+         case-independence. In UTF-mode with UCP support, this uses the new data
+         to handle characters with more than one other case.
+     (c) A bug that is fixed as a result of (b) is that codepoints less than 256
+         whose other case is greater than 256 are now correctly matched
+         caselessly. Previously, the high codepoint matched the low one, but not
+         vice versa.
+     (d) The processing of \h, \H, \v, and \ in character classes now makes use
+         of the new class addition function, using character lists defined as
+         macros alongside the case definitions of 20 above.
+     (e) Caseless back references now work with characters that have more than
+         one other case.
+     (f) General caseless matching of characters with more than one other case
+         is supported.
+. Unicode character properties were updated from Unicode 6.2.0
+. Improved CMake support under Windows. Patch by Daniel Richard G.
+. Add support for 32-bit character strings, and UTF-32
+. Major JIT compiler update (code refactoring and bugfixing).
+     Experimental Sparc 32 support is added.
+. Applied a modified version of Daniel Richard G's patch to create
+     pcre.h.generic and config.h.generic by "make" instead of in the
+     PrepareRelease script.
+. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
+     pcre_compile.c when checking for a zero character.
+. Introducing a native interface for JIT. Through this interface, the compiled
+     machine code can be directly executed. The purpose of this interface is to
+     provide fast pattern matching, so several sanity checks are not performed.
+     However, feature tests are still performed. The new interface provides
+.4x speedup compared to the old one.
+. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
+     the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
+     was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
+. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
+     greater than 0x7fffffff (which cannot be represented in UTF-8, even under
+     the "old" RFC 2279). Instead, it ended up passing a negative length to
+     pcre_exec().
+. Add support for GCC's visibility feature to hide internal functions.
+. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
+     "unknown -C option" after outputting 0 or 1.
+. There is now support for generating a code coverage report for the test
+     suite in environments where gcc is the compiler and lcov is installed. This
+     is mainly for the benefit of the developers.
+. If PCRE is built with --enable-valgrind, certain memory regions are marked
+     unaddressable using valgrind annotations, allowing valgrind to detect
+     invalid memory accesses. This is mainly for the benefit of the developers.
+. (*UTF) can now be used to start a pattern in any of the three libraries.
+. Give configure error if --enable-cpp but no C++ compiler found.
+ Version 8.31 06-July-2012
+ -------------------------
+.  Fixing a wrong JIT test case and some compiler warnings.
+.  Removed a bashism from the RunTest script.
+.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
+     to unsigned type, result still unsigned" that was given by an MS compiler
+     on encountering the code "-sizeof(xxx)".
+.  Partial matching support is added to the JIT compiler.
+.  Fixed several bugs concerned with partial matching of items that consist
+     of more than one character:
+     (a) /^(..)\1/ did not partially match "aba" because checking references was
+         done on an "all or nothing" basis. This also applied to repeated
+         references.
+     (b) \R did not give a hard partial match if \r was found at the end of the
+         subject.
+     (c) \X did not give a hard partial match after matching one or more
+         characters at the end of the subject.
+     (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
+         a partial match for the string "\r".
+     (e) When newline was set to CRLF, the metacharacter "." did not recognize
+         a partial match for a CR character at the end of the subject string.
+.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
+     running pcretest, the text "(JIT)" added to the output whenever JIT is
+     actually used to run the match.
+.  Individual JIT compile options can be set in pcretest by following -s+[+]
+     or /S+[+] with a digit between 1 and 7.
+.  OP_NOT now supports any UTF character not just single-byte ones.
+.  (*MARK) control verb is now supported by the JIT compiler.
+. The command "./RunTest list" lists the available tests without actually
+     running any of them. (Because I keep forgetting what they all are.)
+. Add PCRE_INFO_MAXLOOKBEHIND.
+. Applied a (slightly modified) user-supplied patch that improves performance
+     when the heap is used for recursion (compiled with --disable-stack-for-
+     recursion). Instead of malloc and free for each heap frame each time a
+     logical recursion happens, frames are retained on a chain and re-used where
+     possible. This sometimes gives as much as 30% improvement.
+. As documented, (*COMMIT) is now confined to within a recursive subpattern
+     call.
+. As documented, (*COMMIT) is now confined to within a positive assertion.
+. It is now possible to link pcretest with libedit as an alternative to
+     libreadline.
+. (*COMMIT) control verb is now supported by the JIT compiler.
+. The Unicode data tables have been updated to Unicode 6.1.0.
+. Added --file-list option to pcregrep.
+. Added binary file support to pcregrep, including the -a, --binary-files,
+     -I, and --text options.
+. The madvise function is renamed for posix_madvise for QNX compatibility
+     reasons. Fixed by Giuseppe D'Angelo.
+. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
+. Changed the option for creating symbolic links for 16-bit man pages from
+     -s to -sf so that re-installing does not cause issues.
+. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
+. Fixed a very old bug in pcretest that caused errors with restarted DFA
+     matches in certain environments (the workspace was not being correctly
+     retained). Also added to pcre_dfa_exec() a simple plausibility check on
+     some of the workspace data at the beginning of a restart.
+. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
+     was not doing so when it should - probably a typo introduced by SVN 528
+     (change 8.10/14).
+. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
+     \w+ when the character tables indicated that \x{c4} was a word character.
+     There were several related cases, all because the tests for doing a table
+     lookup were testing for characters less than 127 instead of 255.
+. If a pattern contains capturing parentheses that are not used in a match,
+     their slots in the ovector are set to -1. For those that are higher than
+     any matched groups, this happens at the end of processing. In the case when
+     there were back references that the ovector was too small to contain
+     (causing temporary malloc'd memory to be used during matching), and the
+     highest capturing number was not used, memory off the end of the ovector
+     was incorrectly being set to -1. (It was using the size of the temporary
+     memory instead of the true size.)
+. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
+     ovector size, it uses memory at the end of the block that it has got.
+. Check for an overlong MARK name and give an error at compile time. The
+     limit is 255 for the 8-bit library and 65535 for the 16-bit library.
+. JIT compiler update.
+. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
+     Rill for the patch.
+. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
+. Variable renamings in the PCRE-JIT compiler. No functionality change.
+. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
+     SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
+     was enabled.
+. Improve JIT code generation for greedy plus quantifier.
+. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
+to "aa" instead of to an empty string. The bug affected repeated groups
+     that could potentially match an empty string.
+. Optimizing single character iterators in JIT.
+. Wide characters specified with \uxxxx in JavaScript mode are now subject to
+     the same checks as \x{...} characters in non-JavaScript mode. Specifically,
+     codepoints that are too big for the mode are faulted, and in a UTF mode,
+     disallowed codepoints are also faulted.
+. If PCRE was compiled with UTF support, in three places in the DFA
+     matcher there was code that should only have been obeyed in UTF mode, but
+     was being obeyed unconditionally. In 8-bit mode this could cause incorrect
+     processing when bytes with values greater than 127 were present. In 16-bit
+     mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
+     both cases the values are those that cannot be the first data item in a UTF
+     character. The three items that might have provoked this were recursions,
+     possessively repeated groups, and atomic groups.
+. Ensure that libpcre is explicitly listed in the link commands for pcretest
+     and pcregrep, because some OS require shared objects to be explicitly
+     passed to ld, causing the link step to fail if they are not.
+. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
+     mode, patterns that started with \h* or \R* might be incorrectly matched.
+ Version 8.30 04-February-2012
+ -----------------------------
+.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
+     name is defined in ctype.h.
+.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
+     only in quite long subpatterns.
+.  Removed the function pcre_info(), which has been obsolete and deprecated
+     since it was replaced by pcre_fullinfo() in February 2000.
+.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
+     match a (*MARK), and the match failed at the start of the subject, a
+     reference to memory before the start of the subject could occur. This bug
+     was introduced by fix 17 of release 8.21.
+.  A reference to an unset group with zero minimum repetition was giving
+     totally wrong answers (in non-JavaScript-compatibility mode). For example,
+     /(another)?(\1?)test/ matched against "hello world test". This bug was
+     introduced in release 8.13.
+.  Add support for 16-bit character strings (a large amount of work involving
+     many changes and refactorings).
+.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
+     command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
+     from a file.
+.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
+     rounding is not applied in this particular case).
+.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
+     if they appear, or are escaped, in patterns.
+. Get rid of a number of -Wunused-but-set-variable warnings.
+. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
+     "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
+     Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
+     also returns the mark "x". This bug applied to capturing parentheses,
+     non-capturing parentheses, and atomic parentheses. It also applied to some
+     assertions.
+. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
+     information out of configure.ac instead of relying on pcre.h.generic, which
+     is not stored in the repository.
+. Applied Dmitry V. Levin's patch for a more portable method for linking with
+     -lreadline.
+. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
+. Applied Graycode's patch to put the top-level frame on the stack rather
+     than the heap when not using the stack for recursion. This gives a
+     performance improvement in many cases when recursion is not deep.
+. Experimental code added to "pcretest -C" to output the stack frame size.
+ Version 8.21 12-Dec-2011
+ ------------------------
 .  Updating the JIT compiler.
-Line 13 
 Version 8.21
+Line 621 
 Version 8.21
      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
      calling _pcre_jit_exec. Some extra comments are added.
-.  Mark settings inside atomic groups that do not contain any capturing
+.  (*MARK) settings inside atomic groups that do not contain any capturing
      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
      was introduced by change 18 for 8.20.
-Line 22 
 Version 8.21
+Line 630 
 Version 8.21
 .  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
      This bug was probably introduced by change 9 of 8.13.
 .  While fixing 6 above, I noticed that a number of other items were being
      incorrectly rejected as "not fixed length". This arose partly because newer
      opcodes had not been added to the fixed-length checking code. I have (a)
      corrected the bug and added tests for these items, and (b) arranged for an
      error to occur if an unknown opcode is encountered while checking for fixed
      length instead of just assuming "not fixed length". The items that were
      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
 .  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
      being incorrectly compiled and would have given unpredicatble results.
 .  A possessively repeated subpattern with minimum repeat count greater than
      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
      the first (A) could occur when it should not.
 . Add a cast and remove a redundant test from the code.
 . JIT should use pcre_malloc/pcre_free for allocation.
 . Updated pcre-config so that it no longer shows -L/usr/lib, which seems
      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
      is anything other than /usr, -L is still shown).
 . In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
 . Perl does not support \N without a following name in a [] class; PCRE now
      also gives an error.
 . If a forward reference was repeated with an upper limit of around 2000,
      it caused the error "internal error: overran compiling workspace". The
      maximum number of forward references (including repeats) was limited by the
      internal workspace, and dependent on the LINK_SIZE. The code has been
      rewritten so that the workspace expands (via pcre_malloc) if necessary, and
      the default depends on LINK_SIZE. There is a new upper limit (for safety)
      of around 200,000 forward references. While doing this, I also speeded up
      the filling in of repeated forward references.
 . A repeated forward reference in a pattern such as (a)(?2){2}(.) was
      incorrectly expecting the subject to contain another "a" after the start.
 . When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
      in the match, the SKIP should be ignored. This was not happening; instead
      the SKIP was being treated as NOMATCH. For patterns such as
      /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
      tested.
 . The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
      now much more compatible with Perl, in particular in cases where the result
      is a non-match for a non-anchored pattern. For example, if
      /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
      "m", where previously it did not return a name. A side effect of this
      change is that for partial matches, the last encountered mark name is
      returned, as for non matches. A number of tests that were previously not
      Perl-compatible have been moved into the Perl-compatible test files. The
      refactoring has had the pleasing side effect of removing one argument from
      the match() function, thus reducing its stack requirements.
+. If the /S+ option was used in pcretest to study a pattern using JIT,
+     subsequent uses of /S (without +) incorrectly behaved like /S+.
+. Retrieve executable code size support for the JIT compiler and fixing
+     some warnings.
+. A caseless match of a UTF-8 character whose other case uses fewer bytes did
+     not work when the shorter character appeared right at the end of the
+     subject string.
+. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
+     systems.
+. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
+     output it when the /M option is used in pcretest.
+. The CheckMan script was not being included in the distribution. Also, added
+     an explicit "perl" to run Perl scripts from the PrepareRelease script
+     because this is reportedly needed in Windows.
+. If study data was being save in a file and studying had not found a set of
+     "starts with" bytes for the pattern, the data written to the file (though
+     never used) was taken from uninitialized memory and so caused valgrind to
+     complain.
+. Updated RunTest.bat as provided by Sheri Pierce.
+. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
+. Computation of memory usage for the table of capturing group names was
+     giving an unnecessarily large value.
  Version 8.20 21-Oct-2011
  ------------------------
-Line 1099 
 Version 7.9 11-Apr-09
+Line 1739 
 Version 7.9 11-Apr-09
 .  A pattern that could match an empty string could cause pcregrep to loop; it
      doesn't make sense to accept an empty string match in pcregrep, so I have
      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
-     seems to be how GNU grep behaves.
+     seems to be how GNU grep behaves. [But see later change 40 for release
+.33.]
 .  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
      start or after a newline", because the conditional assertion was not being
-Line 1342 
 Version 7.7 07-May-08
+Line 1983 
 Version 7.7 07-May-08
      containing () gave an internal compiling error instead of "reference to
      non-existent subpattern". Fortunately, when the pattern did exist, the
      compiled code was correct. (When scanning forwards to check for the
-     existencd of the subpattern, it was treating the data ']' as terminating
+     existence of the subpattern, it was treating the data ']' as terminating
      the class, so got the count wrong. When actually compiling, the reference
      was subsequently set up correctly.)

 Legend:



Removed from v.773
 


changed lines


 
Added in v.1354
 Legend:



Removed from v.773
 


changed lines


 
Added in v.1354
-Removed from v.773
+Added in v.1354

	ViewVC Help
Powered by ViewVC 1.1.5