-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix usage of uninitialized memory in swift_addNewDSOImage. #26275
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
Conversation
@swift-ci please test |
Build failed |
Build failed |
This should address https://bugs.swift.org/browse/SR-6848. Couldn't transform the unsafeGet to get because it would produce an infinite loop.
@swift-ci please test linux |
Build failed |
@swift-ci please test macos |
Build failed |
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.
This looks fine to me, thanks!
@mikeash this make sense to you as well? |
@pschuh sorry for the delay. I got buried in mentions while on vacation and am digging out |
Looks good to me! |
@swift-ci please test |
Build failed |
Build failed |
This should address https://bugs.swift.org/browse/SR-6848.
Couldn't transform the unsafeGet to get() because it would produce an infinite loop due to the fact that this gets called in the constructor. All non-reentrant versions will continue to use the safe version.