/[pcre]/code/trunk/doc/pcrejit.3
ViewVC logotype

Diff of /code/trunk/doc/pcrejit.3

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

revision 691 by ph10, Sun Sep 11 14:31:21 2011 UTC revision 748 by ph10, Tue Nov 15 17:44:38 2011 UTC
# Line 28  JIT. The support is limited to the follo Line 28  JIT. The support is limited to the follo
28    ARM v5, v7, and Thumb2    ARM v5, v7, and Thumb2
29    Intel x86 32-bit and 64-bit    Intel x86 32-bit and 64-bit
30    MIPS 32-bit    MIPS 32-bit
31    Power PC 32-bit and 64-bit    Power PC 32-bit and 64-bit (experimental)
32  .sp  .sp
33  If --enable-jit is set on an unsupported platform, compilation fails.  The Power PC support is designated as experimental because it has not been
34    fully tested. If --enable-jit is set on an unsupported platform, compilation
35    fails.
36  .P  .P
37  A program can tell if JIT support is available by calling \fBpcre_config()\fP  A program can tell if JIT support is available by calling \fBpcre_config()\fP
38  with the PCRE_CONFIG_JIT option. The result is 1 when JIT is available, and 0  with the PCRE_CONFIG_JIT option. The result is 1 when JIT is available, and 0
# Line 75  interpretive code. Line 77  interpretive code.
77  If the JIT compiler finds an unsupported item, no JIT data is generated. You  If the JIT compiler finds an unsupported item, no JIT data is generated. You
78  can find out if JIT execution is available after studying a pattern by calling  can find out if JIT execution is available after studying a pattern by calling
79  \fBpcre_fullinfo()\fP with the PCRE_INFO_JIT option. A result of 1 means that  \fBpcre_fullinfo()\fP with the PCRE_INFO_JIT option. A result of 1 means that
80  JIT compilationw was successful. A result of 0 means that JIT support is not  JIT compilation was successful. A result of 0 means that JIT support is not
81  available, or the pattern was not studied with PCRE_STUDY_JIT_COMPILE, or the  available, or the pattern was not studied with PCRE_STUDY_JIT_COMPILE, or the
82  JIT compiler was not able to handle the pattern.  JIT compiler was not able to handle the pattern.
83    .P
84    Once a pattern has been studied, with or without JIT, it can be used as many
85    times as you like for matching different subject strings.
86  .  .
87  .  .
88  .SH "UNSUPPORTED OPTIONS AND PATTERN ITEMS"  .SH "UNSUPPORTED OPTIONS AND PATTERN ITEMS"
# Line 90  supported. Line 95  supported.
95  .P  .P
96  The unsupported pattern items are:  The unsupported pattern items are:
97  .sp  .sp
98    \eC            match a single byte, even in UTF-8 mode    \eC            match a single byte; not supported in UTF-8 mode
99    (?Cn)          callouts    (?Cn)          callouts
   (?(<name>)...  conditional test on setting of a named subpattern  
   (?(R)...       conditional test on whole pattern recursion  
   (?(Rn)...      conditional test on recursion, by number  
   (?(R&name)...  conditional test on recursion, by name  
100    (*COMMIT)      )    (*COMMIT)      )
101    (*MARK)        )    (*MARK)        )
102    (*PRUNE)       ) the backtracking control verbs    (*PRUNE)       ) the backtracking control verbs
# Line 131  execution. Line 132  execution.
132  .rs  .rs
133  .sp  .sp
134  The code that is generated by the JIT compiler is architecture-specific, and is  The code that is generated by the JIT compiler is architecture-specific, and is
135  also position dependent. For those reasons it cannot be saved and restored like  also position dependent. For those reasons it cannot be saved (in a file or
136  the bytecode and other data of a compiled pattern. You should be able run  database) and restored later like the bytecode and other data of a compiled
137  \fBpcre_study()\fP on a saved and restored pattern, and thereby recreate the  pattern. Saving and restoring compiled patterns is not something many people
138  JIT data, but because JIT compilation uses significant resources, it is  do. More detail about this facility is given in the
139  probably not worth doing this.  .\" HREF
140    \fBpcreprecompile\fP
141    .\"
142    documentation. It should be possible to run \fBpcre_study()\fP on a saved and
143    restored pattern, and thereby recreate the JIT data, but because JIT
144    compilation uses significant resources, it is probably not worth doing this;
145    you might as well recompile the original pattern.
146  .  .
147  .  .
148  .\" HTML <a name="stackcontrol"></a>  .\" HTML <a name="stackcontrol"></a>
# Line 256  Cambridge CB2 3QH, England. Line 263  Cambridge CB2 3QH, England.
263  .rs  .rs
264  .sp  .sp
265  .nf  .nf
266  Last updated: 06 September 2011  Last updated: 15 November 2011
267  Copyright (c) 1997-2011 University of Cambridge.  Copyright (c) 1997-2011 University of Cambridge.
268  .fi  .fi
Legend:
Removed from v.691  
changed lines
  Added in v.748
  ViewVC Help
Powered by ViewVC 1.1.5