Fix SPIR-V structured control flow violation for continue in switch inside for-loop #9609
+45
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A
continuestatement inside aswitchnested within aforloop generates invalid SPIR-V that fails validation: "block exits the selection but not via a structured exit."Root Cause
Commit 412d347 added
continueBlockto theexitBlocksset when processing nested constructs but never removed it. This caused the continue block to persist in the global set, affecting subsequent region processing.Changes
slang-ir-eliminate-multilevel-break.cpp: Added cleanup to removecontinueBlockfromexitBlocksafter processing each region, matching the existing cleanup pattern forinfo.exitBlockstests/bugs/for-loop-switch-continue.slang: Added regression testThe fix ensures proper SPIR-V structured control flow by preventing the continue block from leaking across region boundaries.
Original prompt
continueinside aswitchbreaks structured control flow #9585💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.