Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2025-09-30T18:21:27+00:00 2025-09-30T18:21:27+00:00 James Helferty (NVIDIA) jhelferty@nvidia.com 2025-09-30T18:21:27+00:00 urn:sha1:8086adc90b69f3199767c0617e2c429ce6b27f67 Enables all tests/metal/ tests that can be easily enabled. These tests were not originally designed as render tests; they are generally being enabled for pipecleaning purposes, and will not be rigorously testing the corresponding funcitonality. Where they cannot be enabled as render tests, and a metallib test wasn't already enabled, a metallib test was enabled instead (where possible). Fixes #7892 2024-06-14T05:29:35+00:00 ArielG-NV 159081215+ArielG-NV@users.noreply.github.com 2024-06-14T05:29:35+00:00 urn:sha1:2cc96907e4152291e0b6bca78a0bfbc69ddb8839 * Implement for metal `SV_GroupIndex` 1. If we don't have `sv_GroupThreadId` available we create one using `SV_GroupIndex`s location data. 2. We emit code emulating `sv_GroupThreadId` from the same logic that CUDA/CPP uses. * address most review comments Addressed all but two: [1](https://github.com/shader-slang/slang/pull/4385#discussion_r1639058473) and [2](https://github.com/shader-slang/slang/pull/4385#issuecomment-2166934855) I want to enable tests and be sure there is no bugs using CI before I redesign the code so I have a working fallback. * address comment, enable tests enable now functioning tests due to `SV_GroupIndex` working with metal * syntax error with groupThreadID search did `= param` instead of `= i.param` * add `sv_groupid` for test + test fixes * disable test that won't work regardless