Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2022-05-18T17:57:37+00:00 2022-05-18T17:57:37+00:00 Alexey Panteleev alpanteleev@nvidia.com 2022-05-18T17:57:37+00:00 urn:sha1:69cb6e8f300d77e74bd2c7dfe15d12e10b38f512 See https://github.com/shader-slang/slang/issues/2213 2018-05-02T18:40:09+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2018-05-02T18:40:09+00:00 urn:sha1:60bcc6809f57e12f3705cc65cb325b0983b08899 This change adds support for specifying explicit register spaces, like: ```hlsl // Bind to texture register #2 in space #1 Texture2D t : register(t2, space1); ``` I added a test case to confirm that the register space is properly propagated through the Slang reflection API. This change also adds proper error messages for some error/unsupported cases that weren't being diagnosed: * Specifying a completely bogus register "class" (e.g., `register(bad99)`) * Failing to specify a register index (`register(u)`) * Specifying a component mask (`register(t0.x)`) * Using `packoffset` bindings I added test cases to cover all of these, as well as the new errors around support for register `space` bindings. In order to get the existing tests to pass, I had to remove explicit `packoffset` bindings from some DXSDK test shaders. None of these `packoffset` bindings were semantically significant (they matched what the compiler would do anyway, for both Slang and the standard HLSL compiler). Removing them is required for Slang now that we give an explicit error about our lack of `packoffset` support. In a future change we might add logic to either detect semantically insignificant `packoffset`s, or to just go ahead and support them properly (as a general feature on `struct` types).