Merge release/6.2 into main #650
Merged
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
Adds the Metal4 deployment target for MSL.
Add Metal 4 Deployment Target
…fixed groups, when capability is enabled)
Turn on `AppSandboxConflictingValuesEmitsWarning`
Add register app groups build setting
…2244838) (swiftlang#554) (swiftlang#633) The stub executor needs to trampoline to the entry point in the debug dylib. But linking with `-no_exported_symbols` strips it and launching the app fails to find the symbol. Handles both the `LD_EXPORT_SYMBOLS` build setting and manual flags added to `OTHER_LDFLAGS`.
This resolves some builds warnings on Windows, which helps log readability. (Yes I know we could alternatively just disable those warnings, but technically strerror does have thread safety issues and if we're going to fix that it would be nice to just do it in SwiftSystem in one place only)
…4656898) (swiftlang#645) We don't need this right now. Turned out to be more restrictive than necessary.
…nt library (swiftlang#642) * Add support for the libswiftCompatibilitySpan.dylib backward deployment library * Improve handling of Span back-deployment library bundling A couple of related fixes: * Use 26.0 as the fallback version number when SDKSettings doesn't include SwiftSpanMinimumDeploymentTarget * Update tests to expect `--back-deploy-swift-span` and check when it shouldn't be there * Further handling of Swift back deployment + e2e tests Co-authored-by: Owen Voorhees <[email protected]> * Include rpath for the back-deployed Span dylib Co-authored-by: Owen Voorhees <[email protected]> * Drop unnecessary default arguments * Simplify requireXcode26 * Introduce a hack to allow testing Span back-deployment on older Xcode versions Xcode versions that predate Xcode 26 don't include the Span back-deployment library. Introduce a hack to make it easier to still test with those Xcode versions. * copySwiftLibs tests require Xcode 26 for libSwiftCompatibilitySpan.dylib --------- Co-authored-by: Slava Pestov <[email protected]> Co-authored-by: Owen Voorhees <[email protected]>
jakepetroules
requested review from
aciidgh,
mhrawdon,
mirza-garibovic,
neonichu and
owenv
as code owners
|
@swift-ci test |
owenv
approved these changes
Jul 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
No description provided.