<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/tests/autodiff/reverse-inout-param-custom-derivative.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>2024-08-12T21:18:02+00:00</updated>
<entry>
<title>Warn when inout parameter is never written (#4777)</title>
<updated>2024-08-12T21:18:02+00:00</updated>
<author>
<name>venkataram-nv</name>
<email>vedavamadath@nvidia.com</email>
</author>
<published>2024-08-12T21:18:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=20bd48659d0009de5477380c335e2419f4c66f8b'/>
<id>urn:sha1:20bd48659d0009de5477380c335e2419f4c66f8b</id>
<content type='text'>
Addresses #4698 as one approach to diagnose the potential problem.

Emit warnings when a user marks a parameter as `inout` but never writes to it in the function. A new intrinsic function `unmodified(out T)` has been added to explicitly indicate that an `inout` variable will not be modified in the function.

This is only one way to address the specific validation error in #4698. In general it seems that DXC does some more extensive checks on actual struct fields (as opposed to observing arbitrary struct writes), so that will be the next step.</content>
</entry>
<entry>
<title>Fix derivative signature bug in checkDerivativeAttribute. (#2905)</title>
<updated>2023-05-30T17:41:34+00:00</updated>
<author>
<name>Yong He</name>
<email>yonghe@outlook.com</email>
</author>
<published>2023-05-30T17:41:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=5e1974e8cad3396a8c4bedfd63c1ad31b82ec8eb'/>
<id>urn:sha1:5e1974e8cad3396a8c4bedfd63c1ad31b82ec8eb</id>
<content type='text'>
</content>
</entry>
</feed>
