-
Notifications
You must be signed in to change notification settings - Fork 28
Open
Description
The DXC and Clang DXC results are both incorrect in the same way. This is a high likelyhood of a driver bug.
DXC results
Expected:
---
Name: ExpectedOut
Format: UInt32
Stride: 4
Data: [ 1, 0, 1, 1, 1, 0, 0, 0 ]
OutputProps:
Height: 0
Width: 0
Depth: 0
...
Got:
---
Name: Out
Format: UInt32
Stride: 4
Data: [ 1, 0, 0, 0, 1, 0, 0, 0 ]
OutputProps:
Height: 0
Width: 0
Depth: 0
...
Full Hex 64bit representation of Expected Buffer Values:
[ 0x1, 0x0, 0x1, 0x1, 0x1, 0x0, 0x0, 0x0 ]
Full Hex 64bit representation of Actual Buffer Values:
[ 0x1, 0x0, 0x0, 0x0, 0x1, 0x0, 0x0, 0x0 ]
Clang Results
Comparison Rule: BufferExact
Expected:
---
Name: ExpectedOut
Format: UInt32
Stride: 4
Data: [ 1, 0, 1, 1, 1, 0, 0, 0 ]
OutputProps:
Height: 0
Width: 0
Depth: 0
...
Got:
---
Name: Out
Format: UInt32
Stride: 4
Data: [ 1, 0, 0, 0, 1, 0, 0, 0 ]
OutputProps:
Height: 0
Width: 0
Depth: 0
...
Full Hex 64bit representation of Expected Buffer Values:
[ 0x1, 0x0, 0x1, 0x1, 0x1, 0x0, 0x0, 0x0 ]
Full Hex 64bit representation of Actual Buffer Values:
[ 0x1, 0x0, 0x0, 0x0, 0x1, 0x0, 0x0, 0x0 ]
Metadata
Metadata
Assignees
Labels
No labels