Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2024-11-22T23:14:48+00:00 2024-11-22T23:14:48+00:00 Yong He yonghe@outlook.com 2024-11-22T23:14:48+00:00 urn:sha1:43728fbda5b9af19eded18fe82ca67b66cc6d0f7 * Don't treat StrcturedBuffer<IFoo> as a specializable param. * Fix RHI. 2023-12-06T20:05:07+00:00 Yong He yonghe@outlook.com 2023-12-06T20:05:07+00:00 urn:sha1:11111e5733b189127dc2c4934d67693b9bc6e764 * Support visibility control and default to `internal`. * Fix wip. * Fixes. * Fix. * Fix test. * Add legacy language detection and compatibility for existing code. * Add doc. --------- Co-authored-by: Yong He <yhe@nvidia.com> 2022-08-18T06:08:34+00:00 Yong He yonghe@outlook.com 2022-08-18T06:08:34+00:00 urn:sha1:adaea0e993fd8db351b5dad92802e47ed6d0ec77 * Warning on bool to float conversion. * Fix test cases. * Improve. * LanguageServer: don't show constant value for non constant variables. * Fix tests. * Fix warnings in tests. Co-authored-by: Yong He <yhe@nvidia.com> 2021-05-21T23:38:33+00:00 Yong He yonghe@outlook.com 2021-05-21T23:38:33+00:00 urn:sha1:7f8a9994d0bd99a171a1daa0bce46d92c02ccffd Co-authored-by: T. Foley <tfoleyNV@users.noreply.github.com> 2021-03-17T19:55:30+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2021-03-17T19:55:30+00:00 urn:sha1:6e5d85efb9fa5f647f7f0c7ef784a9fd09b29023 * Remove old code paths from render-test Historically, the `render-test` tool was using three different code paths: * One based on `gfx` and manual (non-reflection-based) parameter setting, used for OpenGL, D3D11, D3D12, and Vulkan * One for CPU that used reflection-based parameter setting but shared no code with the first * One for CUDA that used reflection-based parameter setting and shared some, but not all, code with the CPU path Recently we've updated `render-test` to include a fourth option: * Using `gfx` and the "shader object" system it exposes for a unified reflection-based parameter-setting system taht works across OpenGL, D3D11, D3D12, Vulkan, CUDA, and CPU This change removes the first three options and leaves only the single unified path. A sa result, a bunch of code in `render-test` is no longer needed, and the codebase no longer relies on things like the `IDescriptorSet`-related APIs in `gfx`. Several existing tests had to be disabled to make this change possible. Those tests will need to be audited and either re-enabled once we fix issues in the shader object system, or permanently removed if they don't test stuff we intend to support in the long run (e.g., global-scope type parameters, which aren't a clear necessity). * fixup: CUDA detection logic 2021-01-15T20:10:06+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2021-01-15T20:10:06+00:00 urn:sha1:2a5d5b32348c33aac7ca62aa9a4c2bb7cff8e08a This change converts a large number of our existing tests to use the `ShaderObject` support that was added to the `gfx` layer. In many cases, tests were just updated to pass `-shaderobj` and the result Just Worked. In other cases, a `name` attribute had to be added to one or more `TEST_INPUT` lines. For tests that did not work with shader objects "out of the box," I spent a little bit of time trying to get them work, but fell back to letting those tests run in the older mode. Future changes to the infrastructure will be needed to get those additional tests working in the new path. Along with the changes to test files, the following implementation changes were made to get additional tests working: * Because the shader object mode uses explicit register bindings (from reflection), the hacky logic that was offseting `u` registers for D3D12 based on the number of render targets gets disabled (by another hack). * The "flat" reflection information coming from Slang was not correctly reporting "binding ranges" for things that consumed only uniform data (which would be everything on CUDA/CPU), so it was refactored to properly include binding ranges for anything where the type of the field/variable implied a binding range should be created (even if the `LayoutResourceKind` was `::Uniform`). * A few fixes were made to the CUDA implementation of `Renderer`, in order to get additional tests up and running. Most of these changes had to do with texture bindings, which hadn't really been tested previously. In addition, a few changes were made that were attempts at getting more tests working, but didn't actually help. These could be dropped if requested: * As a quality-of-life feature (not being used) the `object` style of `TEST_INPUT` line is upgraded to support inferring the type to use from the type of the input being set. * Any `object` shader input lines get ignored in non-shader-object mode. 2020-11-20T16:34:14+00:00 Yong He yonghe@outlook.com 2020-11-20T16:34:14+00:00 urn:sha1:ee5842a01cdb2bd6cd4acee7214666f180b95d84 * Make witness and RTTI handles lower to `uint2`. And enable some dynamic dispatch tests on D3D/VK. * Bug fixes. 2020-10-23T06:44:11+00:00 Yong He yonghe@outlook.com 2020-10-23T06:44:11+00:00 urn:sha1:6d1fe29cdcbca18d559e302d6427a504d1762173 2020-09-21T15:27:10+00:00 Yong He yonghe@outlook.com 2020-09-21T15:27:10+00:00 urn:sha1:83514bd25160a9af91abc1b9acd7e44657447526 * Enable all dynamic dispatch tests on CUDA. * Fix expected cross-compile test results. 2020-09-10T22:10:11+00:00 Yong He yonghe@outlook.com 2020-09-10T22:10:11+00:00 urn:sha1:e5b796db188416dfc414dab27b92c86b0b53de2b * Allow existential types in `StructuredBuffer` element type. * Handle StructuredBuffer.Load/.Consume methods * Clean up unnecessary changes * Code cleanup * Update test comment