-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Optimize initialization of mostly zeroed aggregates #7542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
vaivaswatha
wants to merge
7
commits into
master
Choose a base branch
from
vaivaswatha/aggr_init_mostly_zero
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
4d8be83
Optimize initialization of mostly zerod aggregates
vaivaswatha 6df1e15
Disable clippy warning for `lower_single_initializer_to_stores`
vaivaswatha dc70331
fix array_simple test
vaivaswatha 70e1a2d
update deployment test
vaivaswatha a8da8aa
Merge branch 'master' into vaivaswatha/aggr_init_mostly_zero
vaivaswatha a0d85d4
Fix bug when almost 0s and repeated arrays
vaivaswatha 101734d
update snap tests
vaivaswatha File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Skipping zero initializers leaves nested init_aggr instructions unlowered
High Severity
When
skip_zeroesis true and an initializer passes theis_runtime_zeroedcheck, the code usescontinueto skip the call tolower_single_initializer_to_stores. However, if the initializer is aNestedInitAggr, this skips the critical cleanup code that removes the nestedinit_aggrinstruction from the IR. Since nested init_aggrs are excluded fromfind_root_init_aggrs, they aren't removed at the end of the pass either. This leaves unloweredInitAggrinstructions in the IR, causing the "InstOp::InitAggr was not lowered" compiler errors shown in the test failures for cases like[0],(0,), andS1 { a: 0 }.Additional Locations (1)
sway-ir/src/optimize/init_aggr_lowering.rs#L470-L474