Skip to content

[Serialization] Allow loading modules built on some SDK variants #58702

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

Merged
merged 1 commit into from
May 6, 2022

Conversation

xymus
Copy link
Contributor

@xymus xymus commented May 5, 2022

When restricting loading swiftmodules to the SDK used to build them, an exception should be made for modules built against an SDK that is a subset of the SDK used when loading the module. For example, a module built with the macOS11 SDK should be loadable by a client targeting the macOS11.secret SDK. In such a case, the swiftmodule file is more likely to be reliable.

This check is still gated behind the ENABLE_RESTRICT_SWIFTMODULE_SDK env var on the driver side. Loosening this check should make it easier to land it. However, this is still not a recommended configuration so we might want to remove this accepted use case in the future and bring back the requirement for an exact SDK name match.

rdar://92827584

@xymus
Copy link
Contributor Author

xymus commented May 5, 2022

@swift-ci Please smoke test

@xymus xymus requested review from tshortli and bnbarham May 5, 2022 23:57
When restricting loading swiftmodules to the SDK used to build them,
an exception should be made for modules built against an SDK that is a subset
of the SDK used when loading the module. In such a case, the swiftmodule
file is more reliable.

rdar://92827584
@xymus xymus force-pushed the accept-more-sdks branch from 219e69e to 1757061 Compare May 6, 2022 00:08
@xymus
Copy link
Contributor Author

xymus commented May 6, 2022

@swift-ci Please smoke test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants