-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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] Broken test llvm/test/CodeGen/SPIRV/debug-info/debug-type-basic.ll #118011
Labels
Comments
Thank you @Keenuts ! |
This was referenced Dec 2, 2024
VyacheslavLevytskyy
added a commit
that referenced
this issue
Dec 3, 2024
The test case llvm/test/CodeGen/SPIRV/debug-info/debug-type-basic.ll fails due to #118011
TIFitis
pushed a commit
to TIFitis/llvm-project
that referenced
this issue
Dec 18, 2024
The test case llvm/test/CodeGen/SPIRV/debug-info/debug-type-basic.ll fails due to llvm#118011
TIFitis
pushed a commit
to TIFitis/llvm-project
that referenced
this issue
Dec 18, 2024
…emantic.Shader.DebugInfo.100 DebugTypeBasic's flags definition (llvm#118333) This PR is to fix llvm#118011 by emitting OpConstant instead of OpConstantNull to conform to NonSemantic.Shader.DebugInfo.100 DebugTypeBasic's flags definition.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since a recent SPIRV-Tools commit (f3c4a5053f1bd34056282e56659659873f9d47ad), this particular test is broken.
The reason is the emitted SPIR-V does this:
The last operand if the
Flags
operand, which form the spec:Since the flag value is 0, we emit an
OpConstantNull
, but this is not accepted by the validator.I'm not sure if that's a validation issue (shall
OpConstantNull %uint
be the same asOpConstant %uint 0
?) or not.Opening an issue in SPIRV-Tools
The text was updated successfully, but these errors were encountered: