/[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 708 by ph10, Fri Sep 23 11:03:03 2011 UTC
# Line 79  JIT compilation was successful. A result Line 79  JIT compilation was successful. A result
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  .P
82  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
83  times as you like for matching different subject strings.  times as you like for matching different subject strings.
84  .  .
85  .  .
# Line 134  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 (in a file or  also position dependent. For those reasons it cannot be saved (in a file or
138  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
139  pattern. Saving and restoring compiled patterns is not something many people  pattern. Saving and restoring compiled patterns is not something many people
140  do. More detail about this facility is given in the  do. More detail about this facility is given in the
141  .\" HREF  .\" HREF
142  \fBpcreprecompile\fP  \fBpcreprecompile\fP
143  .\"  .\"
144  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
145  restored pattern, and thereby recreate the JIT data, but because JIT  restored pattern, and thereby recreate the JIT data, but because JIT
146  compilation uses significant resources, it is probably not worth doing this;  compilation uses significant resources, it is probably not worth doing this;
147  you might as well recompile the original pattern.  you might as well recompile the original pattern.
148  .  .
149  .  .
Legend:
Removed from v.707  
changed lines
  Added in v.708
  ViewVC Help
Powered by ViewVC 1.1.5