oneapi-src / oneapi-src/unified-runtime
igpu fails for a lot of formats in urMemImageCreateWithImageFormatParam.cpp
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
The igpu driver is returning CL_INVALID_IMAGE_FORMAT_DESCRIPTOR for certain order/data type combos. At first I suspected this was just it returning the wrong error code (it's allowed to return CL_IMAGE_FORMAT_NOT_SUPPORTED, and we have code to handle that), but a quick experiment revealed that it is returning the correct error code for a number of formats. Could still be something dodgy with the driver, but it isn't impossible we're doing something wrong - maybe these format combinations are genuinely incompatible and the igpu is the only driver that's validating for that,
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
Start in urMemImageCreateWithImageFormatParam.cpp and reproduce the igpu failures for the reported image format order/data type combinations. Compare the returned errors with the combinations accepted by other drivers and determine whether the combinations are incompatible or mishandled. Done means the expected behavior and required change are established for the affected formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100