forked from neo-ai/tvm
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[AOT] Initial implementation of --unpacked-api (apache#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
- Loading branch information
Showing
10 changed files
with
478 additions
and
63 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.