oneapi-src / oneapi-src/SYCLomatic
migration of dp4a
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- LLVM
- Stars
- 291
- Forks
- 99
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe
I find that dpct::dp4a calls a cuda device function for the cuda backend. Following your implementation, a function may be added for the hip backend https://github.com/intel/llvm/issues/16848
Describe the solution you would like
No response
Describe alternatives you have considered
No response
Additional context
No response
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 dpct::dp4a entry point and the referenced LLVM issue 16848, then trace how the CUDA backend currently invokes the device function. Done means an equivalent function is added for the HIP backend, following the proposed implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100