Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2024-01-24T23:36:49+00:00 2024-01-24T23:36:49+00:00 Yong He yonghe@outlook.com 2024-01-24T23:36:49+00:00 urn:sha1:e7b6de334f320429462a0257e2191ccf3cbc9a0d * [SPIRV] Support `globallycoherent` modifier. * Fix. * Disable executable cooperative vector tests. * Update expected failure. * [SPIRV] Emit varying output index decoration. * Add test. * Update tests. * Fix test. * Emit `SpvExecutionModeEarlyFragmentTests`. * Lower `StructuredBuffer<bool>`. * Support globallycoherent on ByteAddressBuffer. --------- Co-authored-by: Yong He <yhe@nvidia.com> 2023-05-03T03:29:38+00:00 Yong He yonghe@outlook.com 2023-05-03T03:29:38+00:00 urn:sha1:d52376a65f37fcbbb67428b917fd3819436b6dfb * Various dxc/fxc compatibility fixes. * Cleanup. * Fix test cases. * Fix comments. --------- Co-authored-by: Yong He <yhe@nvidia.com> 2020-02-19T22:36:44+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2020-02-19T22:36:44+00:00 urn:sha1:788556aaaab1b5767e24cf86dc2f71fd285c06f5 When a shader only uses `ParameterBlock`s plus a single buffer for root constants: ```hlsl ParameterBlock<A> a; ParameterBlock<B> b; [[vk::push_constant]] cbuffer Stuff { ... } ``` we expect the push-constant buffer should not affect the `space` allocated to the parameter blocks (so `a` should get `space=0`). This behavior wasn't being implemented correctly in `slang-parameter-binding.cpp`. There was logic to ignore certain resource kinds in entry-point parameter lists when computing whether a default space is needed, but the equivalent logic for the global scope only considered parameters that consuem whole register spaces/sets. This change shuffles the code around and makes sure it considers a global push-constant buffer as *not* needing a default space/set. Note that this change will have no impact on D3D targets, where `Stuff` above would always get put in `space0` because for D3D targets a push-constant buffer is no different from any other constant buffer in terms of register/space allocation. One unrelated point that this change brings to mind is the `[[vk::push_constant]]` should ideally also be allowed to apply to an entry point (where it would modify the default/implicit constant buffer). In fact, it could be argued that push-constant allocation should be the *default* for (non-RT) entry point `uniform` parameters (while `[[vk::shader_record]]` should be the default for RT entry point `uniform` parameters).