diff options
author | Tres Popp <tpopp@google.com> | 2021-11-22 10:37:42 +0100 |
---|---|---|
committer | Tres Popp <tpopp@google.com> | 2021-11-22 14:12:09 +0100 |
commit | 106f3074996c69ab732c6371d5ad6b25fcfd4fa5 (patch) | |
tree | a4a8f06f2daaf308780596de25d3fa54d3b8efa8 /lldb/unittests/ScriptInterpreter/Python | |
parent | f7751a3a4218229c59adced4964831f7a57d256d (diff) | |
download | llvm-106f3074996c69ab732c6371d5ad6b25fcfd4fa5.zip llvm-106f3074996c69ab732c6371d5ad6b25fcfd4fa5.tar.gz llvm-106f3074996c69ab732c6371d5ad6b25fcfd4fa5.tar.bz2 |
Rename MlirExecutionEngine lookup to lookupPacked
The purpose of the change is to make clear whether the user is
retrieving the original function or the wrapper function, in line with
the invoke commands. This new functionality is useful for users that
already have defined their own packed interface, so they do not want the
extra layer of indirection, or for users wanting to the look at the
resulting primary function rather than the wrapper function.
All locations, except the python bindings now have a `lookupPacked`
method that matches the original `lookup` functionality. `lookup`
still exists, but with new semantics.
- `lookup` returns the function with a given name. If `bool f(int,int)`
is compiled, `lookup` will return a reference to `bool(*f)(int,int)`.
- `lookupPacked` returns the packed wrapper of the function with the
given name. If `bool f(int,int)` is compiled, `lookupPacked` will return
`void(*mlir_f)(void**)`.
Differential Revision: https://reviews.llvm.org/D114352
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions