-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Rewrite UnsafeRawBufferPointer.Iterator.next #76294
Merged
Merged
Conversation
This file contains 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 function was unavailable in the debugger because it was getting optimized away.
meg-gupta
force-pushed
the
rewritenext
branch
from
September 5, 2024 22:14
11912d2
to
84e0fe5
Compare
@swift-ci please test |
glessard
reviewed
Sep 5, 2024
…p in SIL The current implementation creates a non-natural loop and none of the SIL and LLVM loop passes will work for such loops. We have to find a way to fix this in SIL. Until then, rewrite so we get a natural loop in SIL.
meg-gupta
force-pushed
the
rewritenext
branch
2 times, most recently
from
September 5, 2024 22:39
d9f979b
to
2f37e10
Compare
meg-gupta
changed the title
Rewrite UnsafeRawBufferPointer.Iterator.next to avoid non natural loop in SIL
Rewrite UnsafeRawBufferPointer.Iterator.next
Sep 5, 2024
@swift-ci test |
@swift-ci Please Apple Silicon benchmark |
|
glessard
reviewed
Sep 17, 2024
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.
Nice!
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.
In the SIL generated from the current implementation, it isn't clear to the optimizer that
_position == nil && _end != nil
can never happen. This ends up creating a non-natural loop and none of the SIL and LLVM loop passes work for such loops. We have to find a way to fix this in SIL. Until then, rewrite so we get a natural loop.Note:
UnsafeBufferPointer.Iterator.next
does not have this issue