Fix out of bounds access in anderson2021_test_apps_autoscheduler#7771
Merged
steven-johnson merged 2 commits intohalide:mainfrom Aug 21, 2023
Merged
Fix out of bounds access in anderson2021_test_apps_autoscheduler#7771steven-johnson merged 2 commits intohalide:mainfrom
steven-johnson merged 2 commits intohalide:mainfrom
Conversation
steven-johnson
approved these changes
Aug 17, 2023
Contributor
|
Thanks for the fix! |
ardier
pushed a commit
to ardier/Halide-mutation
that referenced
this pull request
Mar 3, 2024
…ide#7771) * Fix out of bounds access in anderson2021_test_apps_autoscheduler * clang-format
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.
This fixes #7606. If an update stage has fewer pure vars than the pure definition, it can end up reading out of bounds. When reading the size of the update stage's loop, instead of using the corresponding pure dimension, it should just use its index within the update stage's loops.