You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[AOT] Initial implementation of --unpacked-api (#8023)
* [AOT] Initial implementation of --no-typed-operators
Based on the discussions in the AOT embedded improvements RFC, this adds a flag to the target which changes the internal operators to an unpacked API. The unpacked API spreads the input buffers across the operator function, for example:
int32_t operator(void* arg0, void* arg1);
As opposed to the traditional packed API:
int32_t operator(void** args);
Uneffected is the entrypoint function, which retains a packed API for
compatibility with other parts of TVM. This is done by changing the
passes taken by none entrypoint (CallingConv::kEntryPoint) functions.
* Move entrypoint generation outside of main passes
This removes the logic for deciding the entrypoint from the compiler
passes and instead moves it into the metadata code generation. By moving
the generation, we can generate a variety of entrypoints on top of the
compiler output (such as the micro entrypoint discussed in the RFC).
* Use buffers in make_unpacked_api tests
* Enable --no-typed-operators for llvm
* Change --no-typed-operators to --typed-operators=0 to match other options
* Refactor typed-operators lookup into use_typed_operators_
(Also contains minor clean up of output variables)
* Rename --typed-operators to --unpacked-api
(Also moves the entrypoint name to a constant)
* Move all properties into init list to avoid double init
* Remove AutoTVM breaking default and improve clarity
0 commit comments