Repository navigation
[TIRx] Represent device boundaries with region operations - #20566
Merged
Merged
Conversation
Use distinct device entry and internal split regions to preserve lexical scope and target ownership. Route script construction, scope resolution, target binding and host/device extraction through these operators.
tlopex
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Represent device-entry boundaries and the internal host/device splitting envelope with distinct region operations. Reuse ordinary region frames for concise and explicit device-entry syntax, preserving scope-ID resolution and launch ordering.
Carry the target on the internal region while annotating and extracting device functions. Migrate the associated builder, printer, analysis, lowering, and backend consumers and remove the superseded attribute paths.