| 96 |
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 |
| 97 |
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 |
| 98 |
<b>pcre_fullinfo()</b> with the PCRE_INFO_JIT option. A result of 1 means that |
<b>pcre_fullinfo()</b> with the PCRE_INFO_JIT option. A result of 1 means that |
| 99 |
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 |
| 100 |
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 |
| 101 |
JIT compiler was not able to handle the pattern. |
JIT compiler was not able to handle the pattern. |
| 102 |
</P> |
</P> |
| 103 |
|
<P> |
| 104 |
|
Once a pattern has been studied, with or without JIT, it can be used as many |
| 105 |
|
times as you like for matching different subject strings. |
| 106 |
|
</P> |
| 107 |
<br><a name="SEC4" href="#TOC1">UNSUPPORTED OPTIONS AND PATTERN ITEMS</a><br> |
<br><a name="SEC4" href="#TOC1">UNSUPPORTED OPTIONS AND PATTERN ITEMS</a><br> |
| 108 |
<P> |
<P> |
| 109 |
The only <b>pcre_exec()</b> options that are supported for JIT execution are |
The only <b>pcre_exec()</b> options that are supported for JIT execution are |
| 149 |
<br><a name="SEC6" href="#TOC1">SAVING AND RESTORING COMPILED PATTERNS</a><br> |
<br><a name="SEC6" href="#TOC1">SAVING AND RESTORING COMPILED PATTERNS</a><br> |
| 150 |
<P> |
<P> |
| 151 |
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 |
| 152 |
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 |
| 153 |
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 |
| 154 |
<b>pcre_study()</b> on a saved and restored pattern, and thereby recreate the |
pattern. Saving and restoring compiled patterns is not something many people |
| 155 |
JIT data, but because JIT compilation uses significant resources, it is |
do. More detail about this facility is given in the |
| 156 |
probably not worth doing this. |
<a href="pcreprecompile.html"><b>pcreprecompile</b></a> |
| 157 |
|
documentation. It should be possible to run <b>pcre_study()</b> on a saved and |
| 158 |
|
restored pattern, and thereby recreate the JIT data, but because JIT |
| 159 |
|
compilation uses significant resources, it is probably not worth doing this; |
| 160 |
|
you might as well recompile the original pattern. |
| 161 |
<a name="stackcontrol"></a></P> |
<a name="stackcontrol"></a></P> |
| 162 |
<br><a name="SEC7" href="#TOC1">CONTROLLING THE JIT STACK</a><br> |
<br><a name="SEC7" href="#TOC1">CONTROLLING THE JIT STACK</a><br> |
| 163 |
<P> |
<P> |
| 273 |
</P> |
</P> |
| 274 |
<br><a name="SEC11" href="#TOC1">REVISION</a><br> |
<br><a name="SEC11" href="#TOC1">REVISION</a><br> |
| 275 |
<P> |
<P> |
| 276 |
Last updated: 06 September 2011 |
Last updated: 23 September 2011 |
| 277 |
<br> |
<br> |
| 278 |
Copyright © 1997-2011 University of Cambridge. |
Copyright © 1997-2011 University of Cambridge. |
| 279 |
<br> |
<br> |