<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/tests/cross-compile/rw-buffer.slang, branch master</title>
<subtitle>Making it easier to work with shaders</subtitle>
<id>https://git.yummers.dev/slang.git/atom?h=master</id>
<link rel='self' href='https://git.yummers.dev/slang.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/'/>
<updated>2023-10-02T10:33:58+00:00</updated>
<entry>
<title>Add SPIRV intrinsics for ShaderExecutionReordering and RW/Buffer. (#3252)</title>
<updated>2023-10-02T10:33:58+00:00</updated>
<author>
<name>Yong He</name>
<email>yonghe@outlook.com</email>
</author>
<published>2023-10-02T10:33:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=ccf2611c024ab12dcccd978f3f501d4ee9fc52bc'/>
<id>urn:sha1:ccf2611c024ab12dcccd978f3f501d4ee9fc52bc</id>
<content type='text'>
* Add SPIRV intrinsics for ShaderExecutionReordering.

* Add intrinsics for `Buffer` and `RWBuffer`.

* Various spirv fixes.

* Marshal bool vector type.

* Inline global constants + OpFOrdNotEqual-&gt;OpFUnordNotEqual.

* Fix.

---------

Co-authored-by: Yong He &lt;yhe@nvidia.com&gt;</content>
</entry>
<entry>
<title>Add support for RWBuffer writes on GLSL/SPIR-V target (#1199)</title>
<updated>2020-02-05T18:16:14+00:00</updated>
<author>
<name>Tim Foley</name>
<email>tfoleyNV@users.noreply.github.com</email>
</author>
<published>2020-02-05T18:16:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=122126c006e53bd48064f220104d425b8bf91ddf'/>
<id>urn:sha1:122126c006e53bd48064f220104d425b8bf91ddf</id>
<content type='text'>
This appears to have been an oversight in the work that added support for `imageStore` as well as atomics when writing to `RWTexture*` and friends. The HLSL/Slang `RWBuffer` type maps to GLSL as an `imageBuffer`, which is effectively just another case of writable texture image (bonus points to anybody who can explain to me the meaningful distinction between an `imageBuffer` and an `image1D`).

This change copies the handling of subscript access (`operator[]`) from textures over to buffers, and adds a test case to confirm that the new handling works for the simple case of setting a buffer element.</content>
</entry>
</feed>
