-
Notifications
You must be signed in to change notification settings - Fork 569
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
spirv-val: Check DebugLine Line/Column are valid #5986
base: main
Are you sure you want to change the base?
spirv-val: Check DebugLine Line/Column are valid #5986
Conversation
d543267
to
5af732a
Compare
It seems these tests are showing the bug I found in GLSL (KhronosGroup/glslang#3863), where things like https://github.com/KhronosGroup/glslang/blob/main/Test/baseResults/spv.debuginfo.implicit_br.glsl.frag.out#L16 are adding extra things to the source, but not updating the Line number to match it |
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.
Seems ok for the most part. Prefer making the accessor more robust generally.
For my own sake, I think DebugSourceContinued can't ever be used as a 'Source' operand so all the lines and columns are relative to a DebugSource instruction.
That is correct, we will always reference the |
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.
Looks ok, but I've restarted the formatting bot.
@alan-baker what did we want to do with Glslang failing, should I try to push and get those fixes in first and then rebase this? (I know we have a protocol for these situations, I just haven't had to do it in awhile) |
You can either fix glslang first if you want or merge this and update glslang to have failing tests until it is fixed. If glslang can be updated first, that's preferable. |
I had to raise issue in Glslang because it would generate
Line
/Column
that didn't actually point to any valid spot in theDebugSource
's textThis adds some validation where if there is a
DebugSource
withText
then anyLine
/Column
must be correct, otherwise every other consume tool (like Validation Layers) need to do this before trying to print out the snippet in the source code