llvm / llvm/offload-test-suite
[Intel Xe][WaveOps] Many of the waveOps intrinsics are failing on the Intel B50 GPU
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18
- Forks
- 39
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 40
Description
We need to investigate this ticket and likely file an internal vendor issue to get the driver fixed.
Failed Tests (18):
OffloadTest-clang-d3d12 :: WaveOps/ComponentAccumulationDataRace.test
OffloadTest-clang-d3d12 :: WaveOps/ComponentDataRace.test
OffloadTest-clang-d3d12 :: WaveOps/WaveActiveSum.fp16.test
OffloadTest-clang-d3d12 :: WaveOps/WaveActiveSum.fp32.test
OffloadTest-clang-d3d12 :: WaveOps/WaveActiveSum.fp64.test
OffloadTest-clang-d3d12 :: WaveOps/WaveActiveSum.int16.test
OffloadTest-clang-d3d12 :: WaveOps/WaveActiveSum.int32.test
OffloadTest-clang-d3d12 :: WaveOps/WaveActiveSum.int64.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixProduct.32.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixProduct.fp16.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixProduct.fp64.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixProduct.int16.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixProduct.int64.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixSum.32.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixSum.fp16.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixSum.fp64.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixSum.int16.test
OffloadTest-clang-d3d12 :: WaveOps/WavePrefixSum.int64.test
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 18 listed OffloadTest-clang-d3d12 WaveOps failures on an Intel B50 GPU. Compare the failing WaveOps tests, including the data-race, active-sum, prefix-product, and prefix-sum cases, to determine whether the failures indicate a driver defect. Done means documenting the cause and filing the internal vendor issue if the driver is responsible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100