Skip to content

[ParseableInterfaces] Stop explicitly optimizing cached modules #23725

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
Apr 4, 2019

Conversation

harlanhaskins
Copy link
Contributor

Previously, we always optimized cached modules. Now, use the flag we're
already preserving to optimize them.

Fixes rdar://46358840

@harlanhaskins
Copy link
Contributor Author

@swift-ci smoke test

@harlanhaskins
Copy link
Contributor Author

@swift-ci please smoke test

Previously, we always optimized cached modules. Now, use the flag we're
already preserving to optimize them.

Fixes rdar://46358840
@harlanhaskins
Copy link
Contributor Author

@swift-ci please smoke test

Copy link
Contributor

@nathawes nathawes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@harlanhaskins
Copy link
Contributor Author

@swift-ci please smoke test

@harlanhaskins harlanhaskins merged commit 272d067 into swiftlang:master Apr 4, 2019
harlanhaskins pushed a commit to harlanhaskins/swift that referenced this pull request Apr 4, 2019
[ParseableInterfaces] Stop explicitly optimizing cached modules
harlanhaskins pushed a commit that referenced this pull request Apr 16, 2019
[ParseableInterfaces] Stop explicitly optimizing cached modules
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