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
0914561f85
vkd3d/tests/hlsl/arithmetic-float-uniform.shader_test

143 lines
2.3 KiB
Plaintext
Raw Normal View History

tests: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
[pixel shader]
uniform float2 a;
float4 main() : SV_TARGET
{
float x = a.x;
float y = a.y;
return float4(x + y, x - y, x * y, x / y);
}
[test]
uniform 0 float4 5.0 15.0 0.0 0.0
vkd3d-shader/dxil: Implement the DXIL BINOP instruction.
2023-10-15 22:41:17 -07:00
draw quad
tests: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
probe all rgba (20.0, -10.0, 75.0, 0.33333333) 1
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: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
uniform float2 a;
float4 main() : SV_TARGET
{
float x = a.x;
float y = a.y;
return float4(x % y, +x, -x, y / x);
}
[test]
uniform 0 float4 5.0 15.0 0.0 0.0
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
todo(sm<4) draw quad
tests: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
probe all rgba (5.0, 5.0, -5.0, 3.0) 1
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: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
uniform float2 a;
float4 main() : SV_TARGET
{
float x = a.x;
float y = a.y;
return float4(x % y, -x % y, x % -y, -x % -y);
}
[test]
uniform 0 float4 42.0 5.0 0.0 0.0
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
todo(sm<4) draw quad
tests: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
probe all rgba (2.0, -2.0, 2.0, -2.0) 16
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: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
uniform float2 a;
float4 main() : SV_TARGET
{
float x = a.x;
float y = a.y;
return float4(x % y, -x % y, x % -y, -x % -y);
}
[test]
uniform 0 float4 45.0 5.0 0.0 0.0
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
todo(sm<4) draw quad
tests: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
probe all rgba (0.0, 0.0, 0.0, 0.0)
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)]
vkd3d-shader/hlsl: Use conditional moves for arithmetic operators instead of branching. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-09-09 11:08:52 -07:00
float4 x, y;
float4 main() : sv_target
{
return x % y;
}
[test]
uniform 0 float4 5.0 -42.1 4.0 45.0
uniform 4 float4 15.0 -5.0 4.1 5.0
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
todo(sm<4) draw quad
vkd3d-shader/dxil: Implement the DXIL BINOP instruction.
2023-10-15 22:41:17 -07:00
probe all rgba (5.0, -2.1, 4.0, 0.0) 6
vkd3d-shader/hlsl: Use conditional moves for arithmetic operators instead of branching. Signed-off-by: Nikolay Sivov <nsivov@codeweavers.com>
2023-09-09 11:08:52 -07:00
tests: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
[require]
% Infinities are not allowed in SM1
shader model >= 4.0
[pixel shader]
uniform float2 a;
float4 main() : SV_TARGET
{
float x = a.x;
float y = a.y;
return x / y;
}
[test]
uniform 0 float4 1.0 0.0 0.0 0.0
vkd3d-shader/dxil: Implement the DXIL BINOP instruction.
2023-10-15 22:41:17 -07:00
draw quad
tests: Test float operations with uniform inputs. The point of the "uniform" variants is to avoid hiding code generation bugs because of the constant folding optimization.
2022-10-14 06:45:04 -07:00
probe all rgba (1e99, 1e99, 1e99, 1e99)
tests/shader-runner: Add 64-bit arithmetic tests.
2023-11-22 06:11:41 -08:00
[require]
shader model >= 5.0
float64
[pixel shader todo]
uniform double2 a;
float4 main() : SV_TARGET
{
double x = a.x;
double y = a.y;
return float4(x + y, x - y, x * y, x / y);
}
[test]
uniform 0 double2 7.5 -2.5
todo(sm<6) draw quad
probe all rgba (5.0, 10.0, -18.75, -3.0)
[pixel shader todo]
uniform double2 a;
float4 main() : SV_TARGET
{
double x = a.x;
double y = a.y;
return x * y;
}
[test]
uniform 0 double2 3.0e-300 2.5e300
todo(sm<6) draw quad
probe all rgba (7.5, 7.5, 7.5, 7.5)
% Note: DXC does not support modulo on doubles.
[pixel shader todo]
uniform double2 a;
float4 main() : SV_TARGET
{
double x = a.x;
double y = a.y;
return x / y;
}
[test]
uniform 0 double2 1.5e300 2.0e299
todo(sm<6) draw quad
probe all rgba (7.5, 7.5, 7.5, 7.5)
Reference in New Issue Copy Permalink