Add a developer guide for exporting to executorch #1219
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
att, the requirement for exporting a quantized model to executorch is mainly that we want to preserve soem high level ops so they can be lowered to executorch ops, examples of ops that are already preserved are quantize_affine/dequantize_affine/choose_qparams_affine which can be matched in executorch for pattern matching, this PR adds an example for how to define and preserve a quantized embedding_byte op, the main util function we use is
torchao.utils._register_custom_op
The expected output is that after export we see some high level ops (such as quantized embedding op) being preserved:
Test Plan:
python tutorials/developer_api_guide/export_to_executorch.py
Reviewers:
Subscribers:
Tasks:
Tags: