[Bug 51181] New: d3d10core:d3d10core fails systematically on AMD GPUs

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51181

Bug ID: 51181
           Summary: d3d10core:d3d10core fails systematically on AMD GPUs
           Product: Wine
           Version: 6.8
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: directx-d3d
          Assignee: [e-mail]
          Reporter: [e-mail]

test_instanced_draw() fails systematically in d3d10core:d3d10core on AMD GPUs
(and sometimes there is a crash that follows):

d3d10core.c:9275: Test failed: Got 0xfff0f010, expected 0xff80f010 at (160, 0),
sub-resource 0.
d3d10core.c:9275: Test failed: Got 0xfff0f040, expected 0xff80f040 at (240, 0),
sub-resource 0.
d3d10core.c:9275: Test failed: Got 0xffaaaacc, expected 0xffbbaacc at (480, 0),
sub-resource 0.
d3d10core.c:9275: Test failed: Got 0xffaaaa90, expected 0xffbbaa90 at (560, 0),
sub-resource 0.

Notice how this failure does not happen on the machines that have other GPUs
such as cw-gtx560 or QEmu VMs, and how this does not depend on the Windows
version or Radeon driver version for that matter:

https://test.winehq.org/data/patterns.html#d3d10core:d3d10core

So it looks like the test expects fails to account for the Radeon driver
results for some reason.

The commit that introduced this test is:

commit fcd549345d96109179b125d31baf9e9073ecf643
Author:     Józef Kucia 
AuthorDate: Mon Nov 6 10:55:20 2017 +0100
Commit:     Alexandre Julliard 
CommitDate: Mon Nov 6 19:37:09 2017 +0100

d3d10core/tests: Add test for SV_InstanceID.

Signed-off-by: Józef Kucia 
    Signed-off-by: Henri Verbeet 
    Signed-off-by: Alexandre Julliard