[PATCH 9/9] d3d11/tests: Add test for typed UAV loads.

[Józef Kucia]

On Tue, Nov 29, 2016 at 4:16 PM, Henri Verbeet <hverbeet at gmail.com> wrote:
> On 29 November 2016 at 12:06, Józef Kucia <jkucia at codeweavers.com> wrote:
>> Signed-off-by: Józef Kucia <jkucia at codeweavers.com>
>> ---
>>  dlls/d3d11/tests/d3d11.c | 326 +++++++++++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 326 insertions(+)
>>
> This fails for me on Windows:
>
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (0, 0).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (1, 0).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (2, 0).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (3, 0).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (0, 1).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (1, 1).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (2, 1).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (3, 1).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (0, 2).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (1, 2).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (2, 2).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (3, 2).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (0, 3).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (1, 3).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (2, 3).
>     d3d11.c:11568: Test failed: Test 1: Got 0x3f000000, expected
> 0x00000000 at (3, 3).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (0, 0).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (1, 0).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (2, 0).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (3, 0).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (0, 1).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (1, 1).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (2, 1).
>     d3d11.c:11568: Test failed: Test 5: Got 0x00000010, expected
> 0x00000000 at (3, 1).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (0, 2).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (1, 2).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (2, 2).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (3, 2).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (0, 3).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (1, 3).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (2, 3).
>     d3d11.c:11568: Test failed: Test 5: Got 0xffffffff, expected
> 0x00000000 at (3, 3).
>
>

FWIW, this runs fine on Windows 10 with ATI and Intel GPU. The
failures are for reading from a UAV register which has no UAV.