KhronosGroup / KhronosGroup/OpenCL-TTL
Whether it can support the mobile GPU well?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 43
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I learned from the Adreno GPU optimization manual(https://developer.qualcomm.com/download/adrenosdk/adreno-opencl-programming-guide.pdf?referrer=node/6114):
Avoid using the function called async_work_group_copy. It is often tricky for the compiler to generate the optimal code to load local memory, and better for developers to write code that manually loads data into local memory
Can you do some special optimization for mobile GPUs?
Thanks~~
Contributor guide
No contributing guide indexed for this repository
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
No source file or test is named. Start by locating uses of async_work_group_copy and reading the linked Adreno OpenCL programming guide, then identify how mobile-GPU behavior can be measured in this library. Done would require an agreed optimization scope and benchmark evidence on the target mobile GPU.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100