File: execution-engine.rst

package info (click to toggle)
llvmlite 0.44.0-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,736 kB
  • sloc: python: 12,771; cpp: 3,146; sh: 185; makefile: 183
file content (112 lines) | stat: -rw-r--r-- 3,696 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
================
Execution engine
================

.. currentmodule:: llvmlite.binding


The execution engine is where actual code generation and execution happen. At
present a single execution engine, ``MCJIT``, is exposed.


Functions
=========

* .. function:: create_mcjit_compiler(module, target_machine, use_lmm=None)

     Create a MCJIT-powered engine from the given *module* and
     *target_machine*.

     *lmm* controls whether the llvmlite memory manager is used. If not
     supplied, the default choice for the platform will be used (``True`` on
     64-bit ARM systems, ``False`` otherwise).

     * *module* does not need to contain any code.
     * Returns a :class:`ExecutionEngine` instance.


* .. function:: check_jit_execution()

     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:: ExecutionEngine

   A wrapper around an LLVM execution engine. The following
   methods and properties are available:

   * .. method:: add_module(module)

        Add the *module*---a :class:`ModuleRef` instance---for
        code generation. When this method is called, ownership
        of the module is transferred to the execution engine.

   * .. method:: finalize_object()

        Make sure all modules owned by the execution engine are
        fully processed and usable for execution.

   * .. method:: get_function_address(name)

        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.

   * .. method:: get_global_value_address(name)

        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.

   * .. method:: remove_module(module)

        Remove the *module*---a :class:`ModuleRef` instance---from
        the modules owned by the execution engine. This allows
        releasing the resources owned by the module without
        destroying the execution engine.

    * .. method:: add_object_file(object_file)

        Add the symbols from the specified object file to the execution
        engine.

        * *object_file* str or :class:`ObjectFileRef`: a path to the object file
            or a object file instance. Object file instance is not usable after this
            call.

   * .. method:: 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, buffer)`` arguments:

          * *module* is a :class:`ModuleRef` instance.
          * *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 :class:`ModuleRef` instance 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.

   * .. attribute:: target_data

        The :class:`TargetData` used by the execution engine.