/[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 707 by ph10, Fri Sep 23 10:32:53 2011 UTC revision 717 by ph10, Wed Oct 5 15:58:51 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 79  JIT compilation was successful. A result Line 81  JIT compilation was successful. A result
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  .P
84  Once a pattern has been studied, with or without JIT, it can be used as many  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.  times as you like for matching different subject strings.
86  .  .
87  .  .
# Line 134  execution. Line 136  execution.
136  .rs  .rs
137  .sp  .sp
138  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
139  also position dependent. For those reasons it cannot be saved (in a file or  also position dependent. For those reasons it cannot be saved (in a file or
140  database) and restored later like the bytecode and other data of a compiled  database) and restored later like the bytecode and other data of a compiled
141  pattern. Saving and restoring compiled patterns is not something many people  pattern. Saving and restoring compiled patterns is not something many people
142  do. More detail about this facility is given in the  do. More detail about this facility is given in the
143  .\" HREF  .\" HREF
144  \fBpcreprecompile\fP  \fBpcreprecompile\fP
145  .\"  .\"
146  documentation. It should be possible to run \fBpcre_study()\fP on a saved and  documentation. It should be possible to run \fBpcre_study()\fP on a saved and
147  restored pattern, and thereby recreate the JIT data, but because JIT  restored pattern, and thereby recreate the JIT data, but because JIT
148  compilation uses significant resources, it is probably not worth doing this;  compilation uses significant resources, it is probably not worth doing this;
149  you might as well recompile the original pattern.  you might as well recompile the original pattern.
150  .  .
151  .  .
# Line 265  Cambridge CB2 3QH, England. Line 267  Cambridge CB2 3QH, England.
267  .rs  .rs
268  .sp  .sp
269  .nf  .nf
270  Last updated: 23 September 2011  Last updated: 05 October 2011
271  Copyright (c) 1997-2011 University of Cambridge.  Copyright (c) 1997-2011 University of Cambridge.
272  .fi  .fi
Legend:
Removed from v.707  
changed lines
  Added in v.717
  ViewVC Help
Powered by ViewVC 1.1.5