-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Don't require a strict revision match in LLDB #61628
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
Conversation
@swift-ci test |
Note that LLDB implements its own check for the compiler version and it will also warn unless all but the last digit match. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. If the difference is just in a minor version numbers, should we keep part of the check for LLDB, just looser?
For release-management purposes during development, LLDB's embedded Swift compiler's version number can sometimes be off-by-one in the last digit compared to the Swift compiler. This patch restores the old behavior from before 1718362. rdar://101299168
cf883af
to
3cc2831
Compare
@swift-ci test and merge |
I forgot to update lldb-moduleimport-test. |
@swift-ci test and merge |
1 similar comment
@swift-ci test and merge |
…5545) Pass `requiresRevisionMatch` argument to `validateSerializedAST` after it was introduced in Swift: swiftlang/swift#61628
…5545) Pass `requiresRevisionMatch` argument to `validateSerializedAST` after it was introduced in Swift: swiftlang/swift#61628 (cherry picked from commit 1bfddbc)
…wiftlang#5545) Pass `requiresRevisionMatch` argument to `validateSerializedAST` after it was introduced in Swift: swiftlang/swift#61628 (cherry picked from commit 1bfddbc)
For release-management purposes during development, LLDB's embedded Swift compiler's version number can sometimes be off-by-one in the last digit compared to the Swift compiler.
This patch restores the old behavior from before 1718362.
rdar://101299168