PennyLaneAI / PennyLaneAI/catalyst
Add a `phase_accurate` option to the compiler and classify existing optimizations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 234
- Forks
- 84
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 66
Description
Since we might not want to restrict ourselves to purely phase-accurate optimizations, it might be nice to add an option to the compiler that controls whether phase-inaccurate optimizations are applied as well.
We'd have to decide what the default is. Currently, the optimization referenced in this issue is phase inaccurate:
Originally posted by @dime10 in #1827
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 the compiler's optimization pipeline and the phase-inaccurate optimization referenced from issue #1827. Determine how a phase_accurate option should control these optimizations and what its default should be. Done means the option is defined and existing optimizations are classified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100