Skip to content

Arm backend: Add support for TOSA 1.0 serializer #10135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 14, 2025

Conversation

per
Copy link
Collaborator

@per per commented Apr 14, 2025

Adapt serialization and TOSA graph handling to be able to handle 1.0. Also install TOSA pip package for 1.0 alongside 0.80.

Test plan

Validate that 0.80 TOSA version test still work with the 1.0 package installed.

cc @digantdesai @freddan80 @zingo @oscarandersson8218

Adapt serialization and TOSA graph handling to be able to handle 1.0.
Also install TOSA pip package for 1.0 alongside 0.80.

Signed-off-by: Per Åstrand <[email protected]>
Change-Id: I1ec5fe5836d1aa2d343048a13a85de522da04386
@per per requested a review from digantdesai as a code owner April 14, 2025 11:12
Copy link

pytorch-bot bot commented Apr 14, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/10135

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit ca242fc with merge base 8e89094 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 14, 2025
@per per requested a review from zingo April 14, 2025 11:12
@zingo zingo added the partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm label Apr 14, 2025
@zingo zingo merged commit a260704 into pytorch:main Apr 14, 2025
168 of 170 checks passed
Comment on lines +91 to +94
if isinstance(tosa_spec, tosa_specification.Tosa_0_80):
import tosa_tools.v0_80.serializer.tosa_serializer as ts # type: ignore
elif isinstance(tosa_spec, tosa_specification.Tosa_1_00):
import serializer.tosa_serializer as ts # type: ignore
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIUC in the future, the serializer will support older versions of TOSA, and we will delete the v0.80 serializer, right? If yes, what is the ETA?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the 0.80 should be deleted when 1.0 has landed and is stable.

keyprocedure pushed a commit to keyprocedure/executorch that referenced this pull request Apr 21, 2025
Adapt serialization and TOSA graph handling to be able to handle 1.0.
Also install TOSA pip package for 1.0 alongside 0.80.

### Test plan
Validate that 0.80 TOSA version test still work with the 1.0 package
installed.

Signed-off-by: Per Åstrand <[email protected]>
@per per deleted the tosa_1_0_serializer branch May 15, 2025 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm topic: not user facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants