<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/tests/spirv/debug-var-generic-param.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>2025-09-10T07:14:05+00:00</updated>
<entry>
<title>Check if debugVar for is debuggable types in the legalization pass (#8326)</title>
<updated>2025-09-10T07:14:05+00:00</updated>
<author>
<name>Gangzheng Tong</name>
<email>tonggangzheng@gmail.com</email>
</author>
<published>2025-09-10T07:14:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=2020a102e9e0ea2f39a0f2b2a75085c3607ce734'/>
<id>urn:sha1:2020a102e9e0ea2f39a0f2b2a75085c3607ce734</id>
<content type='text'>
## Problem
When generic functions with debug variables were specialized with
concrete types containing non-debuggable fields (e.g.,
`StructuredBuffer`), the IR cloning process would create invalid
`DebugVar` instructions without checking if the substituted types
remained debuggable.

## Solution
This fix adds a defensive check in the legalization pass that removes
the debugVar created for the non-debuggable types.

---------

Co-authored-by: slangbot &lt;ellieh+slangbot@nvidia.com&gt;
Co-authored-by: slangbot &lt;186143334+slangbot@users.noreply.github.com&gt;</content>
</entry>
</feed>
