Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2025-09-02T23:43:48+00:00 2025-09-02T23:43:48+00:00 James Helferty (NVIDIA) jhelferty@nvidia.com 2025-09-02T23:43:48+00:00 urn:sha1:f02b08490aa905f42a8d90381db84b1f8e409c0c Changes default for render-test to sm_6_5. Since sm_6_5 is the new default, remove the -use-dxil option, add -use-dxcb option Remove -use-dxil option from all test cases. Add -use-dxcb to two tests that needed it. Fixes #7611 2025-08-25T05:19:37+00:00 Harsh Aggarwal (NVIDIA) haaggarwal@nvidia.com 2025-08-25T05:19:37+00:00 urn:sha1:53fa12e1b522a229006595001421caa62e22eba8 2025-08-25T05:19:10+00:00 Harsh Aggarwal (NVIDIA) haaggarwal@nvidia.com 2025-08-25T05:19:10+00:00 urn:sha1:67cf1403496ed80edd26c2e0368ddd851e09103a 2025-07-03T12:30:38+00:00 Mukund Keshava mkeshava@nvidia.com 2025-07-03T12:30:38+00:00 urn:sha1:141eac9eb4400cf94c0a076f339e1d43ed652306 Enable intrinsic tests for cuda. Most of these tests were either disabled or just not enabled for cuda. Fixes #7592 Co-authored-by: Ellie Hermaszewska <ellieh@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-11-11T21:45:23+00:00 Theresa Foley tfoleyNV@users.noreply.github.com 2021-11-11T21:45:23+00:00 urn:sha1:6f523dd95d1f16003c7ed1d4a9e1da0cba0ea76c First, we have a CUDA-only test that simply needed a format name to be changed to match the new conventions in `gfx`. Second, we have one of the "active mask" tests that seems to produce different results locally for developers (under Vulkan) than it does on CI. This is almost certainly down to differences in GPUs and/or drivers. The inconsistency ultimately proves the point that I was trying to make when I wrote those tests - the "active mask" concept is effectively meaningless as exposed in D3D and Vulkan because it has not been specified in a way that allows programmers to reason about its value, and drivers have implemented wildly different interpretations of its supposed semantics for so long that there is no real hope of turning `WaveGetActiveMask()` into something that returns a well-defined value in any but the most trivial cases. TLDR: I disabled that test for Vulkan, which means it is completely disabled. 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-07-24T20:41:43+00:00 jsmall-nvidia jsmall@nvidia.com 2020-07-24T20:41:43+00:00 urn:sha1:17d0da23ada17e60b037d0d642fa292d194d8d06 Co-authored-by: Tim Foley <tfoleyNV@users.noreply.github.com> 2020-07-23T13:37:58+00:00 jsmall-nvidia jsmall@nvidia.com 2020-07-23T13:37:58+00:00 urn:sha1:cf503553eb44f104072d8add4069f8352f7bad22 * Clean up device when VKRenderer dtor is run. Added destroy methods to VulkanSwapChain & VulkanDeviceQueue * Small fixes around testing if DeviceQueue is valid. * Disable active-mask tests. Different drivers appear to change the results. 2020-06-05T17:00:15+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2020-06-05T17:00:15+00:00 urn:sha1:3bb780724830ae830657a47e4eba008a4c0f4ff7 * Fixes for active mask synthesis + tests There are two fixes here: * The code generation that follows active mask synthesis was requiring CUDA SM architecture version 7.0 for one of the introduced instructions, but not all of them. This change centralizes the handling of upgrading the required CUDA SM architecture version, and makes sure that the instructions introduced by active mask synthesis request version 7.0. * The tests for active mask synthesis were not flagged as requiring the `cuda_sm_7_0` feature when invoking `render-test-tool`, which meant they run but produce unexpected results when invoked on a GPU without the required semantics for functions like `__ballot_sync()`. This change adds the missing `-render-feature cuda_sm_7_0` to those tests. * fixup: mark more tests that rely on implicit active mask