/[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 706 by ph10, Mon Sep 12 15:59:57 2011 UTC revision 707 by ph10, Fri Sep 23 10:32:53 2011 UTC
# Line 78  can find out if JIT execution is availab Line 78  can find out if JIT execution is availab
78  JIT compilation 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
79  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
80  JIT compiler was not able to handle the pattern.  JIT compiler was not able to handle the pattern.
81    .P
82    Once a pattern has been studied, with or without JIT, it can be used as many
83    times as you like for matching different subject strings.
84  .  .
85  .  .
86  .SH "UNSUPPORTED OPTIONS AND PATTERN ITEMS"  .SH "UNSUPPORTED OPTIONS AND PATTERN ITEMS"
# Line 131  execution. Line 134  execution.
134  .rs  .rs
135  .sp  .sp
136  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
137  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
138  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
139  \fBpcre_study()\fP on a saved and restored pattern, and thereby recreate the  pattern. Saving and restoring compiled patterns is not something many people
140  JIT data, but because JIT compilation uses significant resources, it is  do. More detail about this facility is given in the
141  probably not worth doing this.  .\" HREF
142    \fBpcreprecompile\fP
143    .\"
144    documentation. It should be possible to run \fBpcre_study()\fP on a saved and
145    restored pattern, and thereby recreate the JIT data, but because JIT
146    compilation uses significant resources, it is probably not worth doing this;
147    you might as well recompile the original pattern.
148  .  .
149  .  .
150  .\" HTML <a name="stackcontrol"></a>  .\" HTML <a name="stackcontrol"></a>
# Line 256  Cambridge CB2 3QH, England. Line 265  Cambridge CB2 3QH, England.
265  .rs  .rs
266  .sp  .sp
267  .nf  .nf
268  Last updated: 06 September 2011  Last updated: 23 September 2011
269  Copyright (c) 1997-2011 University of Cambridge.  Copyright (c) 1997-2011 University of Cambridge.
270  .fi  .fi
Legend:
Removed from v.706  
changed lines
  Added in v.707
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12