oneapi-src / oneapi-src/SYCLomatic
A reporting tool to list the occurrence statistics of non-migrated APIs in a project.
Nobody has claimed this yet.
- Dominant language
- LLVM
- Stars
- 291
- Forks
- 99
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
The overall CUDA API migration support status is recorded in .csv files under <SYCLomatic/docs/dev_guide/api-mapping-status>and also in this online documentation: CUDA API Migration Support Status — . There are more than 50% of non-migrated APIs can be used by users' CUDA projects. A reporting tool to scan the project code base and list the statistics of non-migrated APIs can help evaluate the migration efforts.
A utility to answer the question - "How many unsupported CUDA APIs have been used in my project" can be useful in an early project study phase.
The initial version - https://github.com/Joel-lin/sycl-mapping-api-scanner/blob/main/README.md
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
Read the linked sycl-mapping-api-scanner README first, then review the CSV files under docs/dev_guide/api-mapping-status and the corresponding online documentation. Define how the project scan should report non-migrated CUDA API usage; done means it answers how many unsupported APIs the project uses.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100