-
Notifications
You must be signed in to change notification settings - Fork 341
Implement precise compiler invocations for SwiftASTContext #7758
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
Implement precise compiler invocations for SwiftASTContext #7758
Conversation
See also swiftlang/swift#69679 |
test with swiftlang/swift#69679 |
9b28c04
to
5b8d9b2
Compare
test with swiftlang/swift#69679 |
@kastiglione @augusto2112 This now ready for review! |
@swift-ci test windows |
To deal with the growing number of incompatible Swift language flags, LLDB's expression evaluator can now precisely match the compiler flags from the current breakpoint instead of attempting to build a single compiler invocation for the entire project. This is now possible for the first time thanks to dwim-print and the generic expression evaluator. The feature can be controlled via a new "symbols.swift-precise-compiler-invocation" setting. rdar://115188886
5b8d9b2
to
f1a7160
Compare
test with swiftlang/swift#69679 |
test with swiftlang/swift#69679 |
2 similar comments
test with swiftlang/swift#69679 |
test with swiftlang/swift#69679 |
@swift-ci test windows |
1 similar comment
@swift-ci test windows |
To deal with the growing number of incompatible Swift language flags,
LLDB's expression evaluator can now precisely match the compiler flags
from the current breakpoint instead of attempting to build a single
compiler invocation for the entire project.
This is now possible for the first time thanks to dwim-print and the
generic expression evaluator. The feature can be controlled via
a new "symbols.swift-precise-compiler-invocation" setting.
rdar://115188886