<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/tests/diagnostics/uninitialized-local-variables.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-01-23T08:06:21+00:00</updated>
<entry>
<title>Fix incorrect resolve of specialization instance (#6162)</title>
<updated>2025-01-23T08:06:21+00:00</updated>
<author>
<name>Jay Kwak</name>
<email>82421531+jkwak-work@users.noreply.github.com</email>
</author>
<published>2025-01-23T08:06:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=a9ce7520e5f1b97b09e5de69455258bef55e10d2'/>
<id>urn:sha1:a9ce7520e5f1b97b09e5de69455258bef55e10d2</id>
<content type='text'>
* Fix incorrect resolve of specialization instance

While checking the uninitialized variables, we were not resolving the
specialized instance correctly. This commit repeats the resolve while
the result is a specialization instance. A new test is added for this:
  tests/diagnostics/uninitialized-generic.slang

After the problem is fixed, it revealed another problem in existing
tests:
  tests/compute/nested-generics2.slang
  tests/diagnostics/uninitialized-local-variables.slang

When a struct has a member variable whose type is a generic type,
we cannot iterate over its member variables yet, because the type
is unknown until the generic function/struct is specialized. We will
have to give up checking for these cases.</content>
</entry>
<entry>
<title>Fix potential test failures due to SPIRV validation failure (#6047)</title>
<updated>2025-01-10T19:01:32+00:00</updated>
<author>
<name>Jay Kwak</name>
<email>82421531+jkwak-work@users.noreply.github.com</email>
</author>
<published>2025-01-10T19:01:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=6437f2d37b08972db5e4515bd124639c2903dda1'/>
<id>urn:sha1:6437f2d37b08972db5e4515bd124639c2903dda1</id>
<content type='text'>
There are a few tests that are currently passing but could fail when
conditions change little bit.

When slang-test runs with `test-server`, the spirv validation fails and
the test gets reported as failed even though they are actually passing.

To avoid the potential problem, this commit adds an empty entry point.

Co-authored-by: Yong He &lt;yonghe@outlook.com&gt;</content>
</entry>
<entry>
<title>Report error on nested functions. (#5792)</title>
<updated>2024-12-09T12:47:16+00:00</updated>
<author>
<name>Yong He</name>
<email>yonghe@outlook.com</email>
</author>
<published>2024-12-09T12:47:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=525412c67ceea9f52a26e42044e99b349ebc2535'/>
<id>urn:sha1:525412c67ceea9f52a26e42044e99b349ebc2535</id>
<content type='text'>
* Report error on nested functions.

* Fix.

---------

Co-authored-by: Ellie Hermaszewska &lt;ellieh@nvidia.com&gt;</content>
</entry>
<entry>
<title>Fix bug with uninititialized warnings in nested scopes (#4677)</title>
<updated>2024-07-18T18:13:26+00:00</updated>
<author>
<name>venkataram-nv</name>
<email>vedavamadath@nvidia.com</email>
</author>
<published>2024-07-18T18:13:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=1677a25f44d6f608c8aecd4e5c0ceeb94573c10e'/>
<id>urn:sha1:1677a25f44d6f608c8aecd4e5c0ceeb94573c10e</id>
<content type='text'>
Previously the warning system ignores undefined variables in nested scopes (blocks in IR).</content>
</entry>
<entry>
<title>Warnings function parameters (#4626)</title>
<updated>2024-07-16T21:54:53+00:00</updated>
<author>
<name>venkataram-nv</name>
<email>vedavamadath@nvidia.com</email>
</author>
<published>2024-07-16T21:54:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=05547e25353dd797791c2937679468d529d832d5'/>
<id>urn:sha1:05547e25353dd797791c2937679468d529d832d5</id>
<content type='text'>
* Handle out/inout functions with separate consideration

* Fixing bug with passing aliasable instructions

* Handle autodiff functions (fwd and rev) in warning system

* Handling interface methods

* Handling ref parameters like out/inout

* Temporary fix to remaining bugs

* Refactoring methods and tests

* Recursive check for empty structs

* Using default initializable interface in tests

* Resolving CI fail</content>
</entry>
</feed>
