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
19aef21369
vkd3d/tests/hlsl/return.shader_test

257 lines
4.4 KiB
Plaintext
Raw Normal View History

tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
% Test early return from the entry point.
[pixel shader]
float4 main() : sv_target
{
return float4(0.1, 0.2, 0.3, 0.4);
return float4(0.5, 0.6, 0.7, 0.8);
}
[test]
draw quad
vkd3d-shader/hlsl: Lower return statements.
2021-09-13 21:08:34 -07:00
probe all rgba (0.1, 0.2, 0.3, 0.4)
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
[pixel shader]
void main(out float4 ret : sv_target)
{
ret = float4(0.1, 0.2, 0.3, 0.4);
return;
ret = float4(0.5, 0.6, 0.7, 0.8);
}
[test]
draw quad
vkd3d-shader/hlsl: Lower return statements.
2021-09-13 21:08:34 -07:00
probe all rgba (0.1, 0.2, 0.3, 0.4)
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform float f;
float4 main() : sv_target
{
if (f < 0.5)
return float4(0.1, 0.2, 0.3, 0.4);
return float4(0.5, 0.6, 0.7, 0.8);
}
[test]
uniform 0 float 0.2
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/hlsl: Lower return statements.
2021-09-13 21:08:34 -07:00
probe all rgba (0.1, 0.2, 0.3, 0.4)
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 0.8
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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
probe all rgba (0.5, 0.6, 0.7, 0.8)
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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform float f;
void main(out float4 ret : sv_target)
{
ret = float4(0.1, 0.2, 0.3, 0.4);
if (f < 0.5)
{
ret += 0.1;
}
else
{
return;
ret += 0.3;
}
ret += 0.1;
}
[test]
uniform 0 float 0.2
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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
probe all rgba (0.3, 0.4, 0.5, 0.6)
uniform 0 float 0.8
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/hlsl: Lower return statements.
2021-09-13 21:08:34 -07:00
probe all rgba (0.1, 0.2, 0.3, 0.4)
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform float f;
void main(out float4 ret : sv_target)
{
ret = float4(0.1, 0.2, 0.3, 0.4);
if (f < 0.3)
{
return;
}
ret += 0.1;
if (f < 0.7)
{
return;
}
ret += 0.3;
}
[test]
uniform 0 float 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
todo(sm<4 | sm>=6) draw quad
vkd3d-shader/hlsl: Lower return statements.
2021-09-13 21:08:34 -07:00
probe all rgba (0.1, 0.2, 0.3, 0.4) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 0.5
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 | sm>=6) draw quad
vkd3d-shader/hlsl: Lower return statements.
2021-09-13 21:08:34 -07:00
probe all rgba (0.2, 0.3, 0.4, 0.5) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 0.9
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 | sm>=6) draw quad
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
probe all rgba (0.5, 0.6, 0.7, 0.8) 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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform float f;
void main(out float4 ret : sv_target)
{
ret = float4(0.1, 0.2, 0.3, 0.4);
if (f < 0.7)
{
if (f < 0.3)
return;
ret += 0.1;
}
ret += 0.3;
}
[test]
uniform 0 float 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
todo(sm<4 | sm>=6) draw quad
vkd3d-shader/hlsl: Lower return statements.
2021-09-13 21:08:34 -07:00
probe all rgba (0.1, 0.2, 0.3, 0.4) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 0.5
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 | sm>=6) draw quad
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
probe all rgba (0.5, 0.6, 0.7, 0.8) 1
uniform 0 float 0.9
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 | sm>=6) draw quad
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
probe all rgba (0.4, 0.5, 0.6, 0.7) 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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
void main(out float4 ret : sv_target)
{
ret = float4(0.1, 0.2, 0.3, 0.4);
for (;;)
{
ret *= 2;
return;
ret *= 3;
}
ret += 0.1;
}
[test]
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/hlsl: Write SM4 break instructions.
2021-09-09 23:53:17 -07:00
probe all rgba (0.2, 0.4, 0.6, 0.8)
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform float f;
void main(out float4 ret : sv_target)
{
int i;
ret = 0.1;
for (i = 0; i < 4; ++i)
{
if (ret.x > f)
return;
ret *= 2;
}
ret = 0.9;
}
[test]
uniform 0 float 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 | sm>=6) draw quad
vkd3d-shader/hlsl: Write SM4 break instructions.
2021-09-09 23:53:17 -07:00
probe all rgba (0.1, 0.1, 0.1, 0.1) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 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
todo(sm<4 | sm>=6) draw quad
vkd3d-shader/hlsl: Write SM4 break instructions.
2021-09-09 23:53:17 -07:00
probe all rgba (0.2, 0.2, 0.2, 0.2) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 0.3
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 | sm>=6) draw quad
vkd3d-shader/hlsl: Extend the liveness of nodes produced outside loops. Otherwise, it is possible that the register used by the temp is overridden by a subsequent instruction within the same loop.
2023-05-10 09:30:39 -07:00
probe all rgba (0.4, 0.4, 0.4, 0.4) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 0.7
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 | sm>=6) draw quad
vkd3d-shader/hlsl: Extend the liveness of nodes produced outside loops. Otherwise, it is possible that the register used by the temp is overridden by a subsequent instruction within the same loop.
2023-05-10 09:30:39 -07:00
probe all rgba (0.8, 0.8, 0.8, 0.8) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 0.9
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 | sm>=6) draw quad
vkd3d-shader/hlsl: Extend the liveness of nodes produced outside loops. Otherwise, it is possible that the register used by the temp is overridden by a subsequent instruction within the same loop.
2023-05-10 09:30:39 -07:00
probe all rgba (0.9, 0.9, 0.9, 0.9) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform float f;
void main(out float4 ret : sv_target)
{
if (f < 0.5)
{
ret = 0.1;
for (;;)
{
ret *= 2;
return;
}
ret *= 3;
return;
}
else
{
ret = 0.4;
}
ret = 0.5;
}
[test]
uniform 0 float 0.2
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/hlsl: Write SM4 break instructions.
2021-09-09 23:53:17 -07:00
probe all rgba (0.2, 0.2, 0.2, 0.2)
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float 0.8
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/hlsl: Allow the final expression in a for loop initializer to be omitted.
2021-09-13 20:40:09 -07:00
probe all rgba (0.5, 0.5, 0.5, 0.5)
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -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: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform float4 f[3];
void main(out float4 ret : sv_target)
{
int i, j;
ret = 0.1;
for (i = 0; i < 3; ++i)
{
for (j = 0; j < 3; ++j)
{
if (ret.x > f[j].x)
return;
}
ret *= 2;
}
ret = 0.9;
}
[test]
uniform 0 float4 0.3 0.0 0.0 0.0
uniform 4 float4 0.0 0.0 0.0 0.0
uniform 8 float4 0.1 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
todo(sm<4 | sm>=6) draw quad
probe all rgba (0.1, 0.1, 0.1, 0.1) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 4 float4 0.35 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
todo(sm<4 | sm>=6) draw quad
probe all rgba (0.2, 0.2, 0.2, 0.2) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 8 float4 0.5 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
todo(sm<4 | sm>=6) draw quad
probe all rgba (0.4, 0.4, 0.4, 0.4) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 0 float4 1.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
todo(sm<4 | sm>=6) draw quad
probe all rgba (0.4, 0.4, 0.4, 0.4) 1
tests: Add more tests for early return from the entry point.
2021-09-11 14:07:31 -07:00
uniform 4 float4 2.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
todo(sm<4 | sm>=6) draw quad
probe all rgba (0.9, 0.9, 0.9, 0.9) 1
Reference in New Issue Copy Permalink