Build Swift-Testing with WMO #81788
Open
Build Swift-Testing with WMO #81788
Conversation
This file contains hidden or 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 tells build-script to build Swift-testing with WMO. This results in a faster build products, but is also necessary for configurations using the legacy swift driver, which would emit an invalid swift interface in non-WMO builds. Fixes: rdar://151357567 (cherry picked from commit 5f2b002)
stmontgomery
approved these changes
May 27, 2025
etcwilde
added
swift 6.2
🍒 release cherry pick
|
@swift-ci please test |
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.
This tells build-script to build Swift-testing with WMO. This results in a faster build products, but is also necessary for configurations using the legacy swift driver, which would emit an invalid swift interface in non-WMO builds.
Testing.swiftinterface:413:2: error: '@_optimize(none)' attribute cannot be applied to stored properties). Building swift-testing with WMO enabled results in a faster library and does not involve the broken merge-modules job.