Bound allocation extents for hoist_storage using loop variables one-by-one #8154
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.
This is a fix for #8141.
As described there, the problem is that
bound_of_expr_in_scope
is not recursive: when the storage is hoisted, the allocation extents may depend on the loop variables, so we find a maximum bound for them usingbound_of_expr_in_scope
and the scope which has intervals for each of the loop variables. However, the loop variables themselves may depend on the other loop variables in which case the extent still may refer to loop variables even after callingbound_of_expr_in_scope
.The fix is to apply
bound_of_expr_in_scope
for each loop variable separately in a reverse order. I wasn't sure if there is a more efficient way to achieve this, but hopefully it isn't so bad, because allocation extents are usually pretty small.