Skip to content

Conversation

@jackzhxng
Copy link
Collaborator

No description provided.

- [XNNPACK](https://pytorch.org/executorch/main/backends-xnnpack.html) - this is the most supported backend and will work with all models.
- [CoreML](https://docs.pytorch.org/executorch/stable/backends-coreml.html)
- Cuda
- [Metal](https://docs.pytorch.org/executorch/stable/backends/mps/mps-overview.html) - current only available with `executorch >= 1.1.0.dev20251017`. Please separately install this nightly to use the Metal backend.
Copy link
Contributor

Choose a reason for hiding this comment

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

This is linking to the MPS backend instead. Also, our instructions are to install executorch from source, not the nightly.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

ET needs to be installed from source for Metal?

Copy link
Contributor

@manuelcandales manuelcandales Nov 12, 2025

Choose a reason for hiding this comment

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

Not particular to Metal. I would say the same for CUDA. Given that we are actively developing these backends, it makes sense to instruct users to install from source (i.e. using the install_executorch.sh script) which is also how things are being tested in CI.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Makes sense, could you suggest some installation instructions? Do we install ET from source before or after Optimum ET, and do we install from tip of main or a specific commit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants