-
Notifications
You must be signed in to change notification settings - Fork 419
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
SPIR-V validation fails for shadow sampler #8413
Comments
Searched through |
Below is complete debug SPIR-V assembly of minimal shader that warns when passed to
Error message:
|
Two things:
2 is moot if 1 is valid? There should be no warning here? I would also expect glslang/shaderc to error out if it was not valid. 🤷 |
Looks like it should be valid. Found test for it in https://github.com/KhronosGroup/glslang/blob/592de6cf78e0fb359fc3e2854c9dc0f3cf6d4820/Test/vulkan.frag#L25 . git blame on that line leads to KhronosGroup/glslang@7d4c9a0 which links to KhronosGroup/GLSL#22 . |
So I am like 95% certain you hit this KhronosGroup/glslang#3653 |
Is it not "just" that the validation added in KhronosGroup/SPIRV-Tools#5695 is too strict? Is there something in the SPIR-V specification that says valid SPIR-V must be what SPIRV-Tools checks for? But then, that would be hard to align with what GLSL (and HLSL?) allow? |
I guess it will depend if there was a case where some hardware vendor actually wasn't doing it correctly, therefor the old "valid" SPIR-V was invalid actually and glsl/hlsl will need to generate different logic... this for sure will require some discussion internally in a SPIR-V meeting to sort out, but hopefully will be sorted out soon |
@martin-ejdestig we pulled in the this hit a LOT of people in the ecosystem |
Verified that I do not get any warnings with ef846ac . |
Environment:
Describe the Issue
After upgrading to Vulkan SDK 1.3.290, VVL outputs the following to debug callback when passing SPIR-V generated from GLSL that uses a shadow sampler to
vkCreateShaderModule()
andvkCreateGraphicsPipelines()
:Relevant SPIR-V code:
Generated from the following GLSL code:
I have not had time to test with a minimum example, the above is extracted from a much larger shader. But I think I have included all the relevant SPIR-V (and GLSL it is generated from) that triggers the error messages.
The text was updated successfully, but these errors were encountered: