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 2017-10-19T18:49:16+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2017-10-19T18:49:16+00:00 urn:sha1:88023aea669f258d66e53eab10215337a7f72853 This is functionality required to support a Falcor bug fix. Most of the code to compute the right semantic name/index for a parameter was already present. This change adds: - Storage for semantic name/index on every `VarLayout` - Note: this is wasteful and should be optimized later - A public API to query the semantic name/index - The contract is that this API returns `NULL` if the parameter had no semantic - A bit of work in `parameter-binding.cpp` to attach semantics to varying input/output when traversing varying parameters. - Note: this is intentionally set up so that it associates semantics even with non-leaf parameters, so that an API user can query the semantic of a `struct` parameter and know that its members will be assigned sequential semantic indices from its starting value. - Support for dumping this information in reflection tests One notable thing that I did *not* change here is that the reflection test fixture doesn't report information on the output of an entry point, even though it really should. That should be fixed in a separate change, though, because it would affect many of the expected outputs.