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

Diff of /code/trunk/ChangeLog

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

revision 979 by ph10, Sun Jun 17 19:08:41 2012 UTC revision 990 by zherczeg, Sun Jul 8 16:32:22 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31 02-June-2012  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    
18    Version 8.31 06-July-2012
19  -------------------------  -------------------------
20    
21  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
# Line 133  Version 8.31 02-June-2012 Line 147  Version 8.31 02-June-2012
147  37. Optimizing single character iterators in JIT.  37. Optimizing single character iterators in JIT.
148    
149  38. Wide characters specified with \uxxxx in JavaScript mode are now subject to  38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
150      the same checks as \x{...} characters in non-JavaScript mode. Specifically,      the same checks as \x{...} characters in non-JavaScript mode. Specifically,
151      codepoints that are too big for the mode are faulted, and in a UTF mode,      codepoints that are too big for the mode are faulted, and in a UTF mode,
152      disallowed codepoints are also faulted.      disallowed codepoints are also faulted.
153    
154  39. If PCRE was compiled with UTF support, in three places in the DFA  39. If PCRE was compiled with UTF support, in three places in the DFA
155      matcher there was code that should only have been obeyed in UTF mode, but      matcher there was code that should only have been obeyed in UTF mode, but
156      was being obeyed unconditionally. In 8-bit mode this could cause incorrect      was being obeyed unconditionally. In 8-bit mode this could cause incorrect
# Line 146  Version 8.31 02-June-2012 Line 160  Version 8.31 02-June-2012
160      character. The three items that might have provoked this were recursions,      character. The three items that might have provoked this were recursions,
161      possessively repeated groups, and atomic groups.      possessively repeated groups, and atomic groups.
162    
163    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
164        and pcregrep, because some OS require shared objects to be explicitly
165        passed to ld, causing the link step to fail if they are not.
166    
167    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
168        mode, patterns that started with \h* or \R* might be incorrectly matched.
169    
170    
171  Version 8.30 04-February-2012  Version 8.30 04-February-2012
172  -----------------------------  -----------------------------

Legend:
Removed from v.979  
changed lines
  Added in v.990

  ViewVC Help
Powered by ViewVC 1.1.5