[silmem2reg] Compute DomTreeLevels lazily. #36956
Merged
Conversation
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
We previously were computing this eagerly meaning that if we did not actually need the DomTreeLevel map, we would calculate it and additionally incur a relatively large malloc for the DenseMap (which stores by default IIRC 64 key value pairs). Now, we do it lazily ensuring that we only compute this if we actually need it (when promoting non-single block stack allocations).
|
@swift-ci smoke test |
|
@swift-ci smoke test Mac OS platform |
|
@swift-ci smoke test osx platform |
|
@swift-ci please smoke test osx platform |
|
@swift-ci Please smoke test macOS platform |
1 similar comment
|
@swift-ci Please smoke test macOS platform |
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.
We previously were computing this eagerly meaning that if we did not actually
need the DomTreeLevel map, we would calculate it and additionally incur a
relatively large malloc for the DenseMap (which stores by default IIRC 64 key
value pairs).
Now, we do it lazily ensuring that we only compute this if we actually need it
(when promoting non-single block stack allocations).