-
Notifications
You must be signed in to change notification settings - Fork 341
[lldb] Fix SwiftASTContext creatiion when swift caching is used #9137
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
[lldb] Fix SwiftASTContext creatiion when swift caching is used #9137
Conversation
@swift-ci please test |
lldb/test/API/lang/swift/clangimporter/caching/TestSwiftClangImporterCaching.py
Outdated
Show resolved
Hide resolved
672b0e2
to
d6a63c6
Compare
@swift-ci please test |
c6ee94c
to
83df1c4
Compare
@swift-ci please test |
83df1c4
to
834b288
Compare
Please test with following pull request: @swift-ci please test |
@swift-ci please test |
@swift-ci please test macOS platform |
@cachemeifyoucan This is on the wrong branch. Can you rebase this on |
I thought you land on stable/2023... first before gets integrate to release/6.0. Sure I can re-target 6.0 and that should auto forward to stable/2023. |
Followup to swiftlang#9088, handle the cc1 flag deserialization when swift caching is enabled. LLDB should ignore all the CAS related options from embedded flags since LLDB doesn't receive the correct CAS configuration and should just load the modules from disk directly. rdar://134090397
b4c84cb
to
81b0f13
Compare
@swift-ci please test |
@swift-ci please test windows platform |
@adrian-prantl Can you approve and merge for release/6.0? |
The LLDB automerger flows in the opposite direction. |
Followup to #9088, handle the cc1 flag deserialization when swift caching is enabled. LLDB should ignore all the CAS related options from embedded flags since LLDB doesn't receive the correct CAS configuration and should just load the modules from disk directly.
rdar://134090397