[TIR] Fix PlanAndUpdateBufferAllocationLocation not visiting constant buffer #13605
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.
#13560 is supposed to change only the order in which buffers are visited, but the created
buffer_alloc_recorder_
misses buffers associated withAllocateConst
nodes. These buffers are not part offunc->buffer_map
, and appear only inread
ormatch_buffer
regions, so they are not caught by existing visitors forBufferLoadNode
andBufferStoreNode
.Since constant buffers are not correctly handled by
PlanAndUpdateBufferAllocationLocation
now, tuning on Hexagon is currently broken with this error. This PR fixes this.Since creating a TVMScript-based test case involving constant buffers (
AllocateConst
) is difficult, I hope we can merge this simple PR without a test case.cc @Hzfengsy @FredJia-intellif