llvm / llvm/offload-test-suite
[Metal] Graphics pipeline don't work when writting to an UAV
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18
- Forks
- 39
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 40
Description
Seems like the Metal graphic pipeline is incorrectly setup as the writes done to a RWStructuredBuffer from a pixel shader are not visible.
This is also the case for DirectX (pending a change in https://github.com/llvm/offload-test-suite/pull/648 ).
Steps to reproduce:
- execute a pixel shader writting to a
RWStructuredBuffer - expect the output to be visible in the dumped pipeline state.
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 by reproducing the pixel-shader case that writes to a RWStructuredBuffer and inspect the Metal graphics pipeline setup and dumped pipeline state. Compare the behavior with the DirectX case and its pending change in llvm/offload-test-suite#648; done means the UAV writes are visible in the dumped output.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100