The execution engine is where actual code generation and execution happen. At
present a single execution engine,
MCJIT, is exposed.
Ensure that the system allows creation of executable memory ranges for JIT-compiled code. If some security mechanism such as SELinux prevents it, an exception is raised. Otherwise the function returns silently.
Calling this function early can help diagnose system configuration issues, instead of letting JIT-compiled functions crash mysteriously.
The ExecutionEngine class¶
- class llvmlite.binding.ExecutionEngine¶
A wrapper around an LLVM execution engine. The following methods and properties are available:
Make sure all modules owned by the execution engine are fully processed and usable for execution.
Return the address of the function name as an integer. It’s a fatal error in LLVM if the symbol of name doesn’t exist.
Return the address of the global value name as an integer. It’s a fatal error in LLVM if the symbol of name doesn’t exist.
- set_object_cache(notify_func=None, getbuffer_func=None)¶
Set the object cache callbacks for this engine.
notify_func, if given, is called whenever the engine has finished compiling a module. It is passed the
module is a
buffer is a bytes object of the code generated for the module.
The return value is ignored.
getbuffer_func, if given, is called before the engine starts compiling a module. It is passed an argument, module, a
ModuleRefinstance of the module being compiled.
It can return
None, in which case the module is compiled normally.
It can return a bytes object of native code for the module, which bypasses compilation entirely.