Create a static core_aten_ops_exception_list
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
Currently, we expose the core_aten_ops_exception_list (link) as a customizable argument. However, it is difficult for users to know which ATen operators are currently not decomposable, which can lead to incorrect argument usage.
The set of ATen operators that are unsupported for decomposition is static and consistent across all models using ExecuTorch. Therefore, it would be beneficial to create a static core_aten_ops_exception_list within the ExecuTorch AOT field to simplify usage and reduce errors.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading exir/capture/_config.py at the current core_aten_ops_exception_list definition, then trace how the ExecuTorch AOT field exposes and consumes it. Done means the static list is available in the AOT field so users no longer need to provide a customizable exception list for the consistent unsupported ATen operators.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100