You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DebugFunction must be located before a function definition based on the layout rule in the debug info spec:
"All other debugging instructions should be located between section 9
(All type declarations (OpTypeXXX instructions), all constant instructions, and
all global variable declarations …) and section 10 (All function declaration)
per the core SPIR-V specification."
However, DebugFunction has a function id as one of its operands which results in "not defined ID" error when we run spirv-val
You could just have the DebugFunction occur after the OpFunctionEnd and it would satisfy the use/def rules. If the debug extension specifically allows new forward references, then the validator should be relaxed.
DebugFunction must be located before a function definition based on the layout rule in the debug info spec:
"All other debugging instructions should be located between section 9
(All type declarations (OpTypeXXX instructions), all constant instructions, and
all global variable declarations …) and section 10 (All function declaration)
per the core SPIR-V specification."
However, DebugFunction has a function id as one of its operands which results in "not defined ID" error when we run spirv-val
outputs
The text was updated successfully, but these errors were encountered: