Re: [v2 2/2] d3d11/tests: Add tests for SM5 instructions gather4_c/gather4_po_c
On 19 May 2017 at 14:31, Sven Hesse <drmccoy(a)drmccoy.de> wrote:
Signed-off-by: Sven Hesse <drmccoy(a)drmccoy.de> --- dlls/d3d11/tests/d3d11.c | 230 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 230 insertions(+)
This fails here: d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 1.00000000e+00, 0.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 0.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 1.00000000e+00, 1.00000000e+00, 0.00000000e+00}. d3d11.c:19637: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 0.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 0.00000000e+00, 0.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 1.00000000e+00, 1.00000000e+00, 0.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {0.00000000e+00, 1.00000000e+00, 1.00000000e+00, 0.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 1.00000000e+00, 1.00000000e+00}. d3d11.c:19658: Test failed: Got {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}, expected {1.00000000e+00, 1.00000000e+00, 1.00000000e+00, 1.00000000e+00}.
On 2017-05-22 12:28:24 +0200, Henri Verbeet wrote:
This fails here:
Huh :/ Okay, unfortunately, I have no idea, sorry. In the logs here, it says: fixme:d3d:wined3d_debug_callback 0x116d30: "Program undefined behavior warning: Sampler object 3 has depth compare enabled but is bound to a non-depth texture, and used by a program that samples it with a shadow sampler. This is undefined behavior.". I guess that message comes directly from my GPU drivers (nvidia binary blob 375.26)? But it says that for several other test cases as well (the message appears 37 times for me), so I'm assuming it's not necessarily the issue here? (That message is also why I went for D32_FLOAT in the first place, because then the message is gone for me, and it still works. Well, for me at least, but apparently not on the Wine testbots.)
On 22 May 2017 at 13:32, Sven Hesse <drmccoy(a)drmccoy.de> wrote:
On 2017-05-22 12:28:24 +0200, Henri Verbeet wrote:
This fails here:
Huh :/ Okay, unfortunately, I have no idea, sorry.
Actually, that may be an issue on my end. I'll look into it some more.
In the logs here, it says: fixme:d3d:wined3d_debug_callback 0x116d30: "Program undefined behavior warning: Sampler object 3 has depth compare enabled but is bound to a non-depth texture, and used by a program that samples it with a shadow sampler. This is undefined behavior.".
I guess that message comes directly from my GPU drivers (nvidia binary blob 375.26)?
Yeah, that's driver specific. IIRC the message is technically correct, although drivers seem to do the right thing in practice.
participants (2)
-
Henri Verbeet -
Sven Hesse