Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2024-02-03T06:28:02+00:00 2024-02-03T06:28:02+00:00 Yong He yonghe@outlook.com 2024-02-03T06:28:02+00:00 urn:sha1:14764896c34b230a5563f48d8b8e565de2f3aa10 * Capability type checking. * Fix. --------- Co-authored-by: Yong He <yhe@nvidia.com> 2023-01-23T14:59:25+00:00 Yong He yonghe@outlook.com 2023-01-23T14:59:25+00:00 urn:sha1:46a4d98baa1d43b33717b4377aefeeaf46b9c2ff Co-authored-by: Yong He <yhe@nvidia.com> 2021-02-24T16:21:37+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2021-02-24T16:21:37+00:00 urn:sha1:d66b30729029bdb43892e05c9c80fd56ac95a24f This operation was added along with the `SV_Barycentrics` system-value input, and allows for a `nointerpolation` varying input to a fragment shader to be fetched at a specific vertex index within the primitive that is causing the fragment shader to be invoked. This change adds support for the new operations in the standard library, and also includes a test case to make sure that we emit it correctly when producing HLSL/DXIL. This change also includes a small bug fix to our emission logic for function parameters so that we properly emit layout-related attributes for varying parameters declared directly on an entry point. (Note that most attribute end up being declared in `struct` types in existing HLSL shaders, and our IR passes produce only global variables for attributes on GLSL; the only case this affects is inidividual scalar/vector attributes declared declared as entry-point parameters, when outputting HLSL) Note that this change only adds support for the new function on the HLSL/DXIL path, and doesn't yet add any cross-compilation support for GLSL/SPIR-V. The reason for this is that the equivalent GLSL feature(s) appear to use a different model to the HLSL version, and we need to invent a suitable approach to align them to make portable code possible.