[5.4] In DI, cache whether a memory object is a box. #37484
Merged
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.
Boxes tend to have a small number of uses, so frequently finding the unique projection isn't too bad. Non-boxes, however, can have a large number of uses: for example, a class instance has expected uses proportionate to the number of stored properties. So if we do a linear scan of the uses on a non-box instruction, we'll scale quadratically.
Fixes SR-14532. 5.4 version of #37328.
Explanation: Avoid a quadratic slowdown in DI in class initializers when a class reference has many uses. This is typical when a class has a large number of properties.
Scope: The change is to Swift’s definitive initialization pass, which is run on all functions
Risk: Low
Testing: Manual; no straightforward way to test future regressions here
Issue: rdar://77217125
Reviewer: Erik Eckstein (on original PR)