[REFACTOR][TIRx] Represent buffer definitions as operation bindings - #20482
Merged
Merged
Conversation
tlopex
approved these changes
Sep 28, 2026
Member
Author
|
@tvm-bot rerun |
Use buffer-returning alloc_buffer and decl_buffer calls with explicit shape, dtype, and scope operands. Preserve buffer metadata and operation arguments through traversal, rewriting, printing, and lowering. Carry the shared DataTypeImm compatibility updates needed by the operation operands.
tqchen
force-pushed
the
buffer-allocation-ops
branch
from
September 29, 2026 16:02
0828ecd to
321962c
Compare
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
2 participants
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 buffer allocation and declaration as ordinary bindings of buffer-returning operation calls. Their shape, data type, and storage scope are explicit operands; declaration also carries its existing pointer operand. Allocation annotations live in call attributes. Update traversal, lowering, code generation, and script construction and printing to consume the shared representation.