[6.3][CMake] Avoid 'swiftc -parse' with stdin to check compiler capability#3291
Merged
rintaro merged 1 commit intoswiftlang:release/6.3from Mar 6, 2026
Conversation
When the host compiler is built with assertions, `swiftc -parse -` hits an assertion failure, which fails the capability checks. (cherry picked from commit cdb8ae3)
Member
Author
|
@swift-ci Please test |
Member
Author
|
@swift-ci Please test macOS |
Member
Author
|
@swift-ci Please test Linux |
nkcsgexi
approved these changes
Mar 5, 2026
hamishknight
approved these changes
Mar 5, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Cherry-pick #3290 into
release/6.3swiftc -parse -with a dummy input via stdin. However, when the host compiler is built with assertions enabled, this triggers an assertion failure, causing all capability checks to fail. Although this is technically a compiler bug, this change works around the issue by using a regular file input insteadswiftc -parse dummy.swift