-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Fix for KeyPathMultiModule test failure #25329
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
Fix for KeyPathMultiModule test failure #25329
Conversation
|
Can somebody take a look at this request? |
|
|
|
@swift-ci Please test |
|
Build failed |
|
Ah, the field is pointer-sized, not always 64 bit. For compatibility on 32-bit platforms, we ought to use |
stdlib/public/core/KeyPath.swift
Outdated
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 should be UInt, for 32-bit portability. LGTM otherwise.
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.
Thanks! Change applied.
5e4c300 to
6ac15e9
Compare
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
This commit changes the pointer of
unresolvedIndirectOffsetfrom size UInt32 to size UInt64, so that it is compatible on both big (s390x) and little endian platforms. It resolves the failure ofstdlib/KeyPathMultiModule.swifton big-endian platform. The related discussion can be found at https://forums.swift.org/t/keypath-test-case-v5-0-failed-on-big-endian-platform/19529