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

Diff of /code/trunk/ChangeLog

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

revision 925 by ph10, Wed Feb 22 14:24:56 2012 UTC revision 1035 by ph10, Mon Sep 10 16:23:12 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31  Version 8.32
5  -----------------------------  ------------
6    
7    1.  Improved JIT compiler optimizations for first character search and single
8        character iterators.
9    
10    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
11        Patch by Daniel Richard G.
12    
13    3.  Single character iterator optimizations in the JIT compiler.
14    
15    4.  Improved JIT compiler optimizations for character ranges.
16    
17    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
18        Reported by Giuseppe D'Angelo.
19    
20    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
21        of a line, was being set incorrectly in cases where .* appeared inside
22        atomic brackets at the start of a pattern, or where there was a subsequent
23        *PRUNE or *SKIP.
24    
25    7.  Improved instruction cache flush for POWER/PowerPC.
26        Patch by Daniel Richard G.
27    
28    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
29        grep:
30    
31        (a) There is now no limit to the number of patterns to be matched.
32    
33        (b) An error is given if a pattern is too long.
34    
35        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
36            are now supported.
37    
38        (d) --exclude-from and --include-from (multiple use) have been added.
39    
40        (e) Exclusions and inclusions now apply to all files and directories, not
41            just to those obtained from scanning a directory recursively.
42    
43        (f) Multiple uses of -f and --file-list are now supported.
44    
45        (g) In a Windows environment, the default for -d has been changed from
46            "read" (the GNU grep default) to "skip", because otherwise the presence
47            of a directory in the file list provokes an error.
48    
49        (h) The documentation has been revised and clarified in places.
50    
51    9.  Improve the matching speed of capturing brackets.
52    
53    10. Changed the meaning of \X so that it now matches a Unicode extended
54        grapheme cluster.
55    
56    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
57        out POSIX threads when JIT support is configured.
58    
59    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
60    
61    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
62        structure could go wrong in environments where size_t is not the same size
63        as int.
64    
65    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
66        set.
67    
68    15. The EBCDIC support had decayed; later updates to the code had included
69        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
70        general tidy up of EBCDIC-related issues, and the documentation was also
71        not quite right. There is now a test that can be run on ASCII systems to
72        check some of the EBCDIC-related things (but is it not a full test).
73    
74    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
75        in a small tidy to the code.
76    
77    
78    
79    Version 8.31 06-July-2012
80    -------------------------
81    
82  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
83    
84  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
85    
86  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied  3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
87      to unsigned type, result still unsigned" that was given by an MS compiler      to unsigned type, result still unsigned" that was given by an MS compiler
88      on encountering the code "-sizeof(xxx)".      on encountering the code "-sizeof(xxx)".
89    
90  4.  Partial matching support is added to the JIT compiler.  4.  Partial matching support is added to the JIT compiler.
91    
92  5.  Fixed several bugs concerned with partial matching of items that consist  5.  Fixed several bugs concerned with partial matching of items that consist
93      of more than one character:      of more than one character:
94    
95      (a) /^(..)\1/ did not partially match "aba" because checking references was      (a) /^(..)\1/ did not partially match "aba" because checking references was
96          done on an "all or nothing" basis. This also applied to repeated          done on an "all or nothing" basis. This also applied to repeated
97          references.          references.
98    
99      (b) \R did not give a hard partial match if \r was found at the end of the      (b) \R did not give a hard partial match if \r was found at the end of the
100          subject.          subject.
101    
102      (c) \X did not give a hard partial match after matching one or more      (c) \X did not give a hard partial match after matching one or more
103          characters at the end of the subject.          characters at the end of the subject.
104    
105      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize      (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
106          a partial match for the string "\r".          a partial match for the string "\r".
107    
108      (e) When newline was set to CRLF, the metacharacter "." did not recognize      (e) When newline was set to CRLF, the metacharacter "." did not recognize
109          a partial match for a CR character at the end of the subject string.          a partial match for a CR character at the end of the subject string.
110    
111  6.  When matching is performed using JIT-compiled code, the flag bit  6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
112      PCRE_EXTRA_USED_JIT is set in the pcre_extra block and can be tested by the      running pcretest, the text "(JIT)" added to the output whenever JIT is
113      caller. This bit is checked by pcretest if JIT is requested by /S++ or -s++      actually used to run the match.
114      (instead of just /S+ or -s+) and the text "(JIT)" added to the output if  
115      the bit is set.  7.  Individual JIT compile options can be set in pcretest by following -s+[+]
   
 7.  Individual JIT compile options can be set in pcretest by following -s+[+]  
116      or /S+[+] with a digit between 1 and 7.      or /S+[+] with a digit between 1 and 7.
117    
118  8.  OP_NOT now supports any UTF character not just single-byte ones.  8.  OP_NOT now supports any UTF character not just single-byte ones.
119    
120    9.  (*MARK) control verb is now supported by the JIT compiler.
121    
122    10. The command "./RunTest list" lists the available tests without actually
123        running any of them. (Because I keep forgetting what they all are.)
124    
125    11. Add PCRE_INFO_MAXLOOKBEHIND.
126    
127    12. Applied a (slightly modified) user-supplied patch that improves performance
128        when the heap is used for recursion (compiled with --disable-stack-for-
129        recursion). Instead of malloc and free for each heap frame each time a
130        logical recursion happens, frames are retained on a chain and re-used where
131        possible. This sometimes gives as much as 30% improvement.
132    
133    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
134        call.
135    
136    14. As documented, (*COMMIT) is now confined to within a positive assertion.
137    
138    15. It is now possible to link pcretest with libedit as an alternative to
139        libreadline.
140    
141    16. (*COMMIT) control verb is now supported by the JIT compiler.
142    
143    17. The Unicode data tables have been updated to Unicode 6.1.0.
144    
145    18. Added --file-list option to pcregrep.
146    
147    19. Added binary file support to pcregrep, including the -a, --binary-files,
148        -I, and --text options.
149    
150    20. The madvise function is renamed for posix_madvise for QNX compatibility
151        reasons. Fixed by Giuseppe D'Angelo.
152    
153    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
154    
155    22. Changed the option for creating symbolic links for 16-bit man pages from
156        -s to -sf so that re-installing does not cause issues.
157    
158    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
159    
160    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
161        matches in certain environments (the workspace was not being correctly
162        retained). Also added to pcre_dfa_exec() a simple plausibility check on
163        some of the workspace data at the beginning of a restart.
164    
165    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
166        was not doing so when it should - probably a typo introduced by SVN 528
167        (change 8.10/14).
168    
169    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
170        \w+ when the character tables indicated that \x{c4} was a word character.
171        There were several related cases, all because the tests for doing a table
172        lookup were testing for characters less than 127 instead of 255.
173    
174    27. If a pattern contains capturing parentheses that are not used in a match,
175        their slots in the ovector are set to -1. For those that are higher than
176        any matched groups, this happens at the end of processing. In the case when
177        there were back references that the ovector was too small to contain
178        (causing temporary malloc'd memory to be used during matching), and the
179        highest capturing number was not used, memory off the end of the ovector
180        was incorrectly being set to -1. (It was using the size of the temporary
181        memory instead of the true size.)
182    
183    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
184        ovector size, it uses memory at the end of the block that it has got.
185    
186    29. Check for an overlong MARK name and give an error at compile time. The
187        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
188    
189    30. JIT compiler update.
190    
191    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
192        Rill for the patch.
193    
194    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
195    
196    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
197    
198    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
199        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
200        was enabled.
201    
202    35. Improve JIT code generation for greedy plus quantifier.
203    
204    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
205        1 to "aa" instead of to an empty string. The bug affected repeated groups
206        that could potentially match an empty string.
207    
208    37. Optimizing single character iterators in JIT.
209    
210    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
211        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
212        codepoints that are too big for the mode are faulted, and in a UTF mode,
213        disallowed codepoints are also faulted.
214    
215    39. If PCRE was compiled with UTF support, in three places in the DFA
216        matcher there was code that should only have been obeyed in UTF mode, but
217        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
218        processing when bytes with values greater than 127 were present. In 16-bit
219        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
220        both cases the values are those that cannot be the first data item in a UTF
221        character. The three items that might have provoked this were recursions,
222        possessively repeated groups, and atomic groups.
223    
224    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
225        and pcregrep, because some OS require shared objects to be explicitly
226        passed to ld, causing the link step to fail if they are not.
227    
228    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
229        mode, patterns that started with \h* or \R* might be incorrectly matched.
230    
231    
232  Version 8.30 04-February-2012  Version 8.30 04-February-2012
233  -----------------------------  -----------------------------

Legend:
Removed from v.925  
changed lines
  Added in v.1035

  ViewVC Help
Powered by ViewVC 1.1.5