-
Notifications
You must be signed in to change notification settings - Fork 722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add extra type null checking to prevent AV #4538
Conversation
❌ Build DirectXShaderCompiler 1.0.1819 failed (commit 312ea271a1 by @bob80905) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few more suggestions while figuring out the testing failure.
As we discussed, the clang built tests are failing due to the unsigned vs signed comparison
tools/clang/test/HLSLFileCheck/hlsl/semantics/legacy/D3D9_effect_ps_6_0Tex2D.hlsl
Outdated
Show resolved
Hide resolved
❌ Build DirectXShaderCompiler 1.0.1821 failed (commit 2bb7c55987 by @bob80905) |
❌ Build DirectXShaderCompiler 1.0.1833 failed (commit bc12669c77 by @bob80905) |
Notes: If resource arg is used, StripFunctionParameter will fail, causing validation failure. Test modifiations are not intended to be kept. Testing would have to be different, ultimately.
❌ Build DirectXShaderCompiler 1.0.1845 failed (commit bd91df379f by @bob80905) |
For unsupported semantic types, grabbing the semantic type would result in a nullptr. There was never a check to see if the type returned was null, and so this PR will prevent AV from happening by skipping the appropriate statements when the semantic returned is null and reporting the issue to the user.
This PR should address #3377