Add descriptive exception handling to linker and program options which are not supported on a CTK version basis + handle in tests
Nobody has claimed this yet.
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
no-cache, for example, is not supported when using an environment with cuda 12.4 . Find a compatibility matrix and apply it to supported options when users construct a LinkerOptions instance.
It is possible that the issue is not related to compatibility, in which case it should be resolved appropriately.
repro:
run cuda core linker tests in an environment with nvjitlink from cuda 12.4
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 with the LinkerOptions construction path and the CUDA core linker tests, then reproduce the no-cache case with nvjitlink from CUDA 12.4. Identify whether the failure is version compatibility or another cause, and finish when unsupported options raise descriptive exceptions and the tests cover the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100