- Feb 17, 2025
-
-
Conor McCarthy authored
The flag is currently ignored in the backend, but the disassembler prints it.
-
Conor McCarthy authored
vkd3d-shader/ir: Handle 16-bit minimum-precision structured TGSM declarations in an IR pass instead of in the backend.
-
Conor McCarthy authored
vkd3d-shader/ir: Handle 16-bit minimum-precision raw TGSM declarations in an IR pass instead of in the backend.
-
Conor McCarthy authored
vkd3d-shader/ir: Handle 16-bit minimum-precision indexable temp declarations in an IR pass instead of in the backend.
-
Conor McCarthy authored
vkd3d-shader/ir: Handle 16-bit minimum-precision immediate constant buffers in an IR pass instead of in the backend.
-
Conor McCarthy authored
To implement native 16-bit support without this change, backends must check a flag in every location where bit width is important to determine if a 16-bit value should be treated as 32-bit. Once all 16-bit minimum precision values are converted in the IR, backends need only check the flag for native 16-bit when enabling capabilities. Conversion also simplifies checking for data type mismatches. Erroneus 16/32 mismatches can cause false error detection in the VSIR validator, but problems may potentially occur in backends too. These changes also bring disassembler output for DXIL minimum-precision shaders into line with that of earlier shader models by printing these values as 32-bit minimum-precision instead of printing what appears to be a native 16-bit shader. The SPIR-V backend currently ignores minimum-precision flags, so setting them has no effect there.
-
- Feb 05, 2025
-
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
- Feb 03, 2025
-
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
vkd3d-shader/tpf: Improve readability of compat mapping in sm4_sysval_semantic_from_semantic_name().
-
Shaun Ren authored
The semantic variables from a patch parameter are split as usual, with the difference being that the semantic variable being added is a patch variable itself, with the type being the split variable type, and its number of control points being equal to the original patch variable's number of control points. It is then stored in the original patch variable as follows: for (i = 0; i < n; ++i) patch[i][f] := <inputpatch-sem-var>[i] where n is the number of control points of "patch", and f is the field index in patch corresponding to "<inputpatch-sem-var>". We use special prefixes, "inputpatch-" or "outputpatch-", when adding the semantic patch variables, in order to distinguish them from non-patch semantic variables of the same name.
-
Shaun Ren authored
In anticipation of the need for is_patch_constant_func in sm4_generate_vsir_reg_from_deref(), in order to generate vsir registers from InputPatch/OutputPatch dereferences.
-
Shaun Ren authored
-
Francisco Casas authored
swprintf() expects the length of the buffer in WCHARs instead of bytes, so ARRAY_SIZE() is used instead of sizeof(). This caused almost all tests to terminate abruptly with the following message, in my machine: *** buffer overflow detected ***: terminated
-
- Jan 29, 2025
-
-
Elizabeth Figura authored
-
Elizabeth Figura authored
There is no harm in defining two variables with the same name.
-
Elizabeth Figura authored
-
Elizabeth Figura authored
Remove the no longer needed code to detect redefinition in this case.
-
Elizabeth Figura authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
Shaun Ren authored
-
- Jan 28, 2025
-
-
Elizabeth Figura authored
-
Conor McCarthy authored
-
Conor McCarthy authored
-
- Jan 27, 2025
-
-
Elizabeth Figura authored
D3DCOMPILE_PACK_MATRIX_ROW_MAJOR takes precedence over D3DCOMPILE_PACK_MATRIX_COLUMN_MAJOR.
-
Conor McCarthy authored
-
Conor McCarthy authored
-