Delegate compiler flags to `cudaq-translate`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 455
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
At this point, I'm inclined to delegate things to cudaq-translate. The issue there is figuring out exactly what to delegate and remove from the driver. There are a lot of backend paths to consider here. Still, there is no reason for the driver to step on cudaq-translate's pipelines any longer.
We can move this to a follow-uo.
Originally posted by @schweitzpgi in https://github.com/NVIDIA/cuda-quantum/pull/5275#discussion_r3866803464
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 comparing the driver and cudaq-translate pipelines, then map the backend paths that currently handle compiler flags. Identify which flag handling can move to cudaq-translate and which driver responsibilities remain; done means the driver no longer duplicates those pipelines and all affected backend paths still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100