On Wed Jan 31 09:32:17 2024 +0000, Zebediah Figura wrote:
Part of the point of passing bools as a value other than 1 or 0 there is that it validated that sm4 was doing the right thing in flushing them to 1 and 0. Why not just flush for sm1 in the shader runner like in 3/5? Also, regardless, I don't think we need a separate "bool" type, we can just use int or uint. Yeah, I mostly see the interface between the CPU program and the shaders as binary, not typed. Specifying a type in the `.shader_test` file is a convenience for humans, but I don't think there should be any magic happening. Rather, I'd use the `only()` syntax you just introduced to specify different inputs depending on the SM:
only(sm<4) uniform 0 float4 1.0 2.0 3.0 4.0
only(sm>=4) uniform 0 uint4 1 2 3 4
How does that feel? -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/616#note_59586