| commit | 94d0e710295131c3680337d8f3339bf091b6d06e | [log] [tgz] |
|---|---|---|
| author | Tres Popp <tpopp@google.com> | Mon Nov 22 10:37:42 2021 +0100 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Nov 22 05:16:17 2021 -0800 |
| tree | e793ade62cf5d1173b34cedbb3c1d8a6fde97ded | |
| parent | 26b80e6d99cb43481ce3e149ffbbe3cf47665c59 [diff] |
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 GitOrigin-RevId: 106f3074996c69ab732c6371d5ad6b25fcfd4fa5
See https://mlir.llvm.org/ for more information.