Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2025-05-17T02:26:44+00:00 2025-05-17T02:26:44+00:00 Jay Kwak 82421531+jkwak-work@users.noreply.github.com 2025-05-17T02:26:44+00:00 urn:sha1:d58243d9041947c99f18b82385e62c082507decb The user can explicitly use Vulkan memory model, or it will be automatically used when cooperative-matrix is used. When vulkan memory model is used, two keywords, "Coherent" and "Volatile", are not allowed. There are many differences regarding atomic and texture but this PR has changes limited to support `globallycoherent` keyword. When variables with `globallycoherent` is used with `OpLoad`, it will use additional options, `MakePointerAvailable|NonPrivatePointer`, that will provide the same effect. For `OpStore`, it will use `MakePointerVisible|NonPrivatePointer`. 2018-11-29T15:48:23+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2018-11-29T15:48:23+00:00 urn:sha1:c3c34bf4ca78caff285fbf5f24c5f355ca040bd1 The `globallycoherent` modifier indicates that resource might be read or written by threads outside of the current thread group, so that any memory barriers that affect it should guarantee coherency at the global memory scope, and not just thread-group scope. The equivalent GLSL modifier appears to be `coherent`. This change adds the front-end modifier, transforms it into an IR-level decoration during lowering, and then checks for the modifier during code emit. Note: this logic may not behave correctly when `globallycoherent` is added to a field in a `struct`, since the modifier would then need to be propagated to any variables created during type legalization. Checking up on that is left to future work. Note: it isn't entirely clear if `globallycoherent` should be treated as a declaration modifier or a type modifier. The point is moot for now because Slang doesn't have any support for type modifiers, but when we get around to that we will need to make a decision.