wine/vkd3d
0
0
Fork 0
mirror of https://gitlab.winehq.org/wine/vkd3d.git synced 2024-11-21 16:46:41 -08:00
Code Issues Packages Projects Releases Wiki Activity
f5ed0d9efd
vkd3d/tests/hlsl/conditional.shader_test

278 lines
5.2 KiB
Plaintext
Raw Normal View History

tests: Use the vulkan runner to run SM1 compilation tests. At the current moment this is a little odd because for SM1 [test] directives are skipped, and the [shader] directives are not executed by the shader_runner_vulkan.c:compile_shader() but by the general shader_runner.c:compile_shader(). So in principle it is a little weird that we go through the vulkan runner. But fret not, because in the future we plan to make the parser agnostic to the language of the tests, so we will get rid of the general shader_runner.c:compile_shader() function and instead call a runner->compile_shader() function, defined for each runner. Granted, most of these may call a generic implementation that uses native compiler in Windows, and vkd3d-shader on Linux, but it would be more conceptually correct.
2023-11-15 12:41:33 -08:00
[pixel shader todo(sm<4)]
tests/shader-runner: Test shaders with dxcompiler. The location of dxcompiler should be set during configuration with 'DXCOMPILER_LIBS=-L/path/to/dxcompiler', and then at runtime with LD_LIBRARY_PATH, WINEPATH or PATH as applicable. A new 'fail(sm<6)' decoration is needed on many shader declarations because dxcompiler succeeds on many shaders which fail with fxc. The opposite case is less common and is flagged with 'fail(sm>=6)'. A few tests cause dxcompiler to crash or hang, so these are avoided using [require], which now skips tests until reset instead of exiting. Also, 'todo(sm<6)' and 'todo(sm>=6)' are used to separate checking of results.
2023-09-14 02:29:24 -07:00
uniform float4 u;
float4 main() : sv_target
tests: Import HLSL conditional tests from Wine. Signed-off-by: Zebediah Figura <zfigura@codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org>
2020-09-30 19:01:21 -07:00
{
tests: Simplify conditional test.
2023-05-07 13:02:03 -07:00
if (u.x > 0.0)
tests: Import HLSL conditional tests from Wine. Signed-off-by: Zebediah Figura <zfigura@codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org>
2020-09-30 19:01:21 -07:00
return float4(0.1, 0.2, 0.3, 0.4);
else
return float4(0.9, 0.8, 0.7, 0.6);
}
[test]
tests: Simplify conditional test.
2023-05-07 13:02:03 -07:00
uniform 0 float4 0.0 0.0 0.0 0.0
tests/shader_runner: Add GLSL support to the GL runner.
2024-03-19 04:36:23 -07:00
todo(sm<4 | glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (0.9, 0.8, 0.7, 0.6)
tests: Simplify conditional test.
2023-05-07 13:02:03 -07:00
uniform 0 float4 0.1 0.0 0.0 0.0
tests/shader_runner: Add GLSL support to the GL runner.
2024-03-19 04:36:23 -07:00
todo(sm<4 | glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (0.1, 0.2, 0.3, 0.4)
tests: Add some tests for "if" statement attributes. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-08-10 00:27:57 -07:00
tests: Use the vulkan runner to run SM1 compilation tests. At the current moment this is a little odd because for SM1 [test] directives are skipped, and the [shader] directives are not executed by the shader_runner_vulkan.c:compile_shader() but by the general shader_runner.c:compile_shader(). So in principle it is a little weird that we go through the vulkan runner. But fret not, because in the future we plan to make the parser agnostic to the language of the tests, so we will get rid of the general shader_runner.c:compile_shader() function and instead call a runner->compile_shader() function, defined for each runner. Granted, most of these may call a generic implementation that uses native compiler in Windows, and vkd3d-shader on Linux, but it would be more conceptually correct.
2023-11-15 12:41:33 -08:00
[pixel shader todo(sm<4)]
tests/shader-runner: Test shaders with dxcompiler. The location of dxcompiler should be set during configuration with 'DXCOMPILER_LIBS=-L/path/to/dxcompiler', and then at runtime with LD_LIBRARY_PATH, WINEPATH or PATH as applicable. A new 'fail(sm<6)' decoration is needed on many shader declarations because dxcompiler succeeds on many shaders which fail with fxc. The opposite case is less common and is flagged with 'fail(sm>=6)'. A few tests cause dxcompiler to crash or hang, so these are avoided using [require], which now skips tests until reset instead of exiting. Also, 'todo(sm<6)' and 'todo(sm>=6)' are used to separate checking of results.
2023-09-14 02:29:24 -07:00
uniform float4 u;
float4 main() : sv_target
tests: Add some tests for "if" statement attributes. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-08-10 00:27:57 -07:00
{
[attr1]
if (u.x > 0.0)
return float4(0.1, 0.2, 0.3, 0.4);
else
return float4(0.9, 0.8, 0.7, 0.6);
}
tests: Use the vulkan runner to run SM1 compilation tests. At the current moment this is a little odd because for SM1 [test] directives are skipped, and the [shader] directives are not executed by the shader_runner_vulkan.c:compile_shader() but by the general shader_runner.c:compile_shader(). So in principle it is a little weird that we go through the vulkan runner. But fret not, because in the future we plan to make the parser agnostic to the language of the tests, so we will get rid of the general shader_runner.c:compile_shader() function and instead call a runner->compile_shader() function, defined for each runner. Granted, most of these may call a generic implementation that uses native compiler in Windows, and vkd3d-shader on Linux, but it would be more conceptually correct.
2023-11-15 12:41:33 -08:00
[pixel shader todo(sm<4)]
tests/shader-runner: Test shaders with dxcompiler. The location of dxcompiler should be set during configuration with 'DXCOMPILER_LIBS=-L/path/to/dxcompiler', and then at runtime with LD_LIBRARY_PATH, WINEPATH or PATH as applicable. A new 'fail(sm<6)' decoration is needed on many shader declarations because dxcompiler succeeds on many shaders which fail with fxc. The opposite case is less common and is flagged with 'fail(sm>=6)'. A few tests cause dxcompiler to crash or hang, so these are avoided using [require], which now skips tests until reset instead of exiting. Also, 'todo(sm<6)' and 'todo(sm>=6)' are used to separate checking of results.
2023-09-14 02:29:24 -07:00
uniform float4 u;
float4 main() : sv_target
tests: Add some tests for "if" statement attributes. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-08-10 00:27:57 -07:00
{
[flatten]
if (u.x > 0.0)
return float4(0.1, 0.2, 0.3, 0.4);
else
return float4(0.9, 0.8, 0.7, 0.6);
}
[test]
uniform 0 float4 0.0 0.0 0.0 0.0
tests/shader_runner: Add GLSL support to the GL runner.
2024-03-19 04:36:23 -07:00
todo(sm<4 | glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (0.9, 0.8, 0.7, 0.6)
tests: Add some tests for "if" statement attributes. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-08-10 00:27:57 -07:00
tests/shader-runner: Test shaders with dxcompiler. The location of dxcompiler should be set during configuration with 'DXCOMPILER_LIBS=-L/path/to/dxcompiler', and then at runtime with LD_LIBRARY_PATH, WINEPATH or PATH as applicable. A new 'fail(sm<6)' decoration is needed on many shader declarations because dxcompiler succeeds on many shaders which fail with fxc. The opposite case is less common and is flagged with 'fail(sm>=6)'. A few tests cause dxcompiler to crash or hang, so these are avoided using [require], which now skips tests until reset instead of exiting. Also, 'todo(sm<6)' and 'todo(sm>=6)' are used to separate checking of results.
2023-09-14 02:29:24 -07:00
[pixel shader fail(sm<6)]
tests: Add some tests for "if" statement attributes. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-08-10 00:27:57 -07:00
float4 u;
float main() : sv_target
{
[branch] [branch]
if (u.x > 0.0)
return float4(0.1, 0.2, 0.3, 0.4);
else
return float4(0.9, 0.8, 0.7, 0.6);
}
vkd3d-shader/hlsl: Parse "if" statement attributes. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-08-10 01:03:49 -07:00
[pixel shader fail todo]
tests: Add some tests for "if" statement attributes. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-08-10 00:27:57 -07:00
float4 u;
float main() : sv_target
{
[branch] [flatten]
if (u.x > 0.0)
return float4(0.1, 0.2, 0.3, 0.4);
else
return float4(0.9, 0.8, 0.7, 0.6);
}
% Using older profiles fails to compile with forced control flow instruction
[require]
shader model >= 3.0
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
[pixel shader]
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
uniform float a;
float4 main() : sv_target
{
if (a < 4)
return float4(1, 2, 3, 4);
return float4(10, 20, 30, 40);
}
[test]
uniform 0 float -2
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (1, 2, 3, 4)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
uniform 0 float 10
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (10, 20, 30, 40)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
[pixel shader]
tests/shader-runner: Test shaders with dxcompiler. The location of dxcompiler should be set during configuration with 'DXCOMPILER_LIBS=-L/path/to/dxcompiler', and then at runtime with LD_LIBRARY_PATH, WINEPATH or PATH as applicable. A new 'fail(sm<6)' decoration is needed on many shader declarations because dxcompiler succeeds on many shaders which fail with fxc. The opposite case is less common and is flagged with 'fail(sm>=6)'. A few tests cause dxcompiler to crash or hang, so these are avoided using [require], which now skips tests until reset instead of exiting. Also, 'todo(sm<6)' and 'todo(sm>=6)' are used to separate checking of results.
2023-09-14 02:29:24 -07:00
uniform float4 u;
float4 main() : sv_target
tests: Add some tests for "if" statement attributes. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-08-10 00:27:57 -07:00
{
[branch]
if (u.x > 0.0)
return float4(0.1, 0.2, 0.3, 0.4);
else
return float4(0.9, 0.8, 0.7, 0.6);
}
[test]
uniform 0 float4 0.0 0.0 0.0 0.0
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (0.9, 0.8, 0.7, 0.6)
vkd3d-shader/hlsl: Remove conditional branching when condition is a compile time constant. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-09-27 10:17:40 -07:00
[pixel shader]
float4 main() : sv_target
{
bool c = false;
float a = -1.0f;
if (c)
return float4(1.0, 2.0, 3.0, 4.0);
else if (a > 0)
return float4(5.0, 6.0, 7.0, 8.0);
else
return float4(9.0, 10.0, 11.0, 12.0);
}
[test]
tests/shader_runner: Add GLSL support to the GL runner.
2024-03-19 04:36:23 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (9.0, 10.0, 11.0, 12.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
[pixel shader]
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
int a, b;
float4 main() : sv_target
{
if (a < b)
return -1.0;
else
return 1.0;
}
[test]
if(sm<4) uniform 0 float 8
if(sm<4) uniform 4 float 9
if(sm>=4) uniform 0 int 8
if(sm>=4) uniform 1 int 9
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (-1.0, -1.0, -1.0, -1.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
if(sm<4) uniform 0 float -3
if(sm<4) uniform 4 float -4
if(sm>=4) uniform 0 int -3
if(sm>=4) uniform 1 int -4
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (1.0, 1.0, 1.0, 1.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
if(sm<4) uniform 0 float 7
if(sm<4) uniform 4 float 7
if(sm>=4) uniform 0 int 7
if(sm>=4) uniform 1 int 7
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (1.0, 1.0, 1.0, 1.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
[pixel shader]
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
int a, b;
float4 main() : sv_target
{
if (a <= b)
return -1.0;
else
return 1.0;
}
[test]
if(sm<4) uniform 0 float 8
if(sm<4) uniform 4 float 9
if(sm>=4) uniform 0 int 8
if(sm>=4) uniform 1 int 9
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (-1.0, -1.0, -1.0, -1.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
if(sm<4) uniform 0 float -3
if(sm<4) uniform 4 float -4
if(sm>=4) uniform 0 int -3
if(sm>=4) uniform 1 int -4
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (1.0, 1.0, 1.0, 1.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
if(sm<4) uniform 0 float 7
if(sm<4) uniform 4 float 7
if(sm>=4) uniform 0 int 7
if(sm>=4) uniform 1 int 7
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (-1.0, -1.0, -1.0, -1.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
[pixel shader]
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
int a, b;
float4 main() : sv_target
{
if (a != b)
return -1.0;
else
return 1.0;
}
[test]
if(sm<4) uniform 0 float -3
if(sm<4) uniform 4 float -2
if(sm>=4) uniform 0 int -3
if(sm>=4) uniform 1 int -2
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (-1.0, -1.0, -1.0, -1.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
if(sm<4) uniform 0 float 4
if(sm<4) uniform 4 float 4
if(sm>=4) uniform 0 int 4
if(sm>=4) uniform 1 int 4
vkd3d-shader/d3dbc: Support SM1 if conditionals. According to the documentation, if_comp is available from 2_x pixel and vertex shaders and, unlike "if bool" it doesn't expect a constant boolean register (from the input signature), so: if_neq cond -cond seems like a convenient way to write these, for profiles above 2.0.
2024-03-26 15:43:54 -07:00
todo(glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (1.0, 1.0, 1.0, 1.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
% Test "if" conditionals, using resource loads to ensure we aren't removing these instruction with optimizations.
[srv 0]
size (2d, 2, 2)
0.0 0.0 0.0 4.0 1.0 0.0 0.0 4.0
0.0 1.0 0.0 4.0 1.0 1.0 0.0 4.0
[sampler 0]
filter linear linear linear
address clamp clamp clamp
[pixel shader todo(sm<4)]
Texture2D tex;
sampler sam;
float a;
float4 main() : sv_target
{
if (a < 4)
return tex.Sample(sam, float2(0, 0));
return float4(1, 2, 3, 4);
}
[test]
uniform 0 float -2
todo(sm<4 | glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (0.0, 0.0, 0.0, 4.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
uniform 0 float 4
todo(sm<4 | glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (1.0, 2.0, 3.0, 4.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
[pixel shader todo(sm<4)]
Texture2D tex;
sampler sam;
float a;
float4 main() : sv_target
{
if (a >= 2)
return tex.Sample(sam, float2(0, 0));
else if (a >= 1)
return tex.Sample(sam, float2(1, 0));
else
return tex.Sample(sam, float2(1, 1));
}
[test]
uniform 0 float 2
todo(sm<4 | glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (0.0, 0.0, 0.0, 4.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
uniform 0 float 1
todo(sm<4 | glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (1.0, 0.0, 0.0, 4.0)
tests: Add additional conditional tests for shader model 3.0.
2024-04-01 16:14:58 -07:00
uniform 0 float 0
todo(sm<4 | glsl) draw quad
tests: Stop probing all pixels when drawing a uniform colour. This is simply unnecessary and wastes time. As part of this, simply remove the "all" directive. Only for a couple of tests is it even potentially interesting to validate all pixels (e.g. nointerpolation.shader_test), and for those "all" is replaced with an explicit (0, 0, 640, 480) rect. In all other cases we just probe (0, 0).
2024-02-10 11:16:22 -08:00
probe (0, 0) rgba (1.0, 1.0, 0.0, 4.0)
Reference in New Issue Copy Permalink