<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/docs/user-guide/a2-target-specific-features.md, 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>2025-06-10T15:02:38+00:00</updated>
<entry>
<title>Fix IR layout of 3-element vectors in cbuffers for -fvk-use-dx-layout (#7282)</title>
<updated>2025-06-10T15:02:38+00:00</updated>
<author>
<name>James Helferty (NVIDIA)</name>
<email>jhelferty@nvidia.com</email>
</author>
<published>2025-06-10T15:02:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=e37202002276b679c5241b2678af612552b06d2c'/>
<id>urn:sha1:e37202002276b679c5241b2678af612552b06d2c</id>
<content type='text'>
* Better handling for 16-byte boundary of d3d cbuffer

Fixes #6921

D3D cbuffers have slightly different packing rules that allow packing
vectors into a 16-byte slot at element alignments, except when
a field would cross a 16-byte boundary. In that case, we need to
realign the field to the next 16-byte boundary.

In particular, this impacts vec3s, which are not a power of two in
size and thus require slightly different alignment logic, compared to
std430 and std140. (Example: a float and float3 should fit together in
that order in a single slot.)

Adds test cases.

Adds documentation page for GLSL target</content>
</entry>
<entry>
<title>Add tables of contents to user guide for use on readthedocs (#6979)</title>
<updated>2025-05-02T16:02:31+00:00</updated>
<author>
<name>aidanfnv</name>
<email>aidanf@nvidia.com</email>
</author>
<published>2025-05-02T16:02:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=87c4ab20abebaf3d2f0e8beb9f71b45eb0b64968'/>
<id>urn:sha1:87c4ab20abebaf3d2f0e8beb9f71b45eb0b64968</id>
<content type='text'>
This change adds hidden (commented out) tables of contents to the index of the User Guide, as well as each of the additional chapters, so that readthedocs will render the User Guide structure.</content>
</entry>
<entry>
<title>Fix user-guide typos (#6789)</title>
<updated>2025-04-11T22:34:07+00:00</updated>
<author>
<name>Gangzheng Tong</name>
<email>gtong@nvidia.com</email>
</author>
<published>2025-04-11T22:34:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=8e6af6259bd1dd47d81c36f0562ff362ca5d42c3'/>
<id>urn:sha1:8e6af6259bd1dd47d81c36f0562ff362ca5d42c3</id>
<content type='text'>
* Fix user-guide typos

Use LLM to scan each of the markdown files to fix typos.
Try not to change anything but the typos in this CL.

* typo not caught by LLM

* add output of ./build_toc.ps1</content>
</entry>
<entry>
<title>Add link to metal docs and regen TOC (#5616)</title>
<updated>2024-11-20T19:47:14+00:00</updated>
<author>
<name>Ellie Hermaszewska</name>
<email>ellieh@nvidia.com</email>
</author>
<published>2024-11-20T19:47:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=54ec7553c20673c541298ac39b95ccd25542aa7a'/>
<id>urn:sha1:54ec7553c20673c541298ac39b95ccd25542aa7a</id>
<content type='text'>
* Add link to metal docs

* Regenerate TOC

---------

Co-authored-by: Yong He &lt;yonghe@outlook.com&gt;</content>
</entry>
<entry>
<title>Document WGSL-specific features (#5571)</title>
<updated>2024-11-19T17:06:29+00:00</updated>
<author>
<name>Anders Leino</name>
<email>aleino@nvidia.com</email>
</author>
<published>2024-11-19T17:06:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=f98579d5ea3a69dd0ed75eeacc017fabfc7cb8e0'/>
<id>urn:sha1:f98579d5ea3a69dd0ed75eeacc017fabfc7cb8e0</id>
<content type='text'>
Issue #5567.

Co-authored-by: Yong He &lt;yonghe@outlook.com&gt;</content>
</entry>
<entry>
<title>Document All Capability Atoms and Profiles (#5008)</title>
<updated>2024-09-05T14:41:35+00:00</updated>
<author>
<name>ArielG-NV</name>
<email>159081215+ArielG-NV@users.noreply.github.com</email>
</author>
<published>2024-09-05T14:41:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=d4aeb18cb348104fa6b036393488df780902a353'/>
<id>urn:sha1:d4aeb18cb348104fa6b036393488df780902a353</id>
<content type='text'>
* Document All Capability Atoms and Profiles

Fixes: #4125

Unimplemented Considerations:
1. This PR does not add support to query all capability-atom's from a command-line option. It is understood that this might be desired, due to this, the logic to generate `docs\user-guide\a3-02-reference-capability-atoms.md` was made to be "command-line friendly" so minimal changes are needed to pipe our documentation into a command-line option if this change is to be added.

Changes:
1. Added a way to document atoms inside `.capdef`. Method to document is described under `source\slang\slang-capabilities.capdef`. The goal is to error if a public atom does not have any form of documentation to ensure we always have up-to-date documentation to guide user on what an atom is/does.
    * The following `.capdef` file syntax was added
        * /// [HEADER_GROUP]
        * /// regular comment
2. When capability generator runs it auto-generates `docs\user-guide\a3-02-reference-capability-atoms.md`
3. Added to the user-guide 3 sections: `Reference`, `Reference -&gt; Capability Profiles`, `Reference -&gt; Capability atoms` section</content>
</entry>
<entry>
<title>User guide page for SPIR-V target specific information (#4815)</title>
<updated>2024-08-31T05:10:19+00:00</updated>
<author>
<name>Jay Kwak</name>
<email>82421531+jkwak-work@users.noreply.github.com</email>
</author>
<published>2024-08-31T05:10:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=3033b4217aac5a6d11bfeee61d896c98abf77dfc'/>
<id>urn:sha1:3033b4217aac5a6d11bfeee61d896c98abf77dfc</id>
<content type='text'>
Adding a user guide page for SPIR-V specific features.</content>
</entry>
</feed>
