-
Notifications
You must be signed in to change notification settings - Fork 344
Initialize the Swift CompilerInstance with the triple from the load commands. #3634
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 |
5c75243
to
ed30e17
Compare
@swift-ci test |
@swift-ci test |
lldb/test/API/lang/swift/deployment_target/TestSwiftDeploymentTarget.py
Outdated
Show resolved
Hide resolved
lldb/test/API/lang/swift/dwarfimporter/C/TestSwiftDWARFImporterC.py
Outdated
Show resolved
Hide resolved
@swift-ci test |
Looks like this breaks linux |
preset=lldb-pull-request |
preset=lldb-pull-request |
@JDevlieghere what am I doing wrong with the preset? |
@swift-ci test |
…ommands. The serialized triple is the triple of the last binary __swiftast section that was processed. Instead of relying on the section contents order, we overwrite the triple in the CompilerInvocation with the triple recovered from the binary.
preset=lldb-pull-request |
preset=lldb-pull-request |
I'm not sure, I thought this is how it's supposed to be used. I'm sure @shahmishal will know! |
@swift-ci test |
The serialized triple is the triple of the last binary __swiftast
section that was processed. Instead of relying on the section contents
order, we overwrite the triple in the CompilerInvocation with the
triple recovered from the binary.
This should fix issues such as thew one reported in https://forums.swift.org/t/lldb-not-honoring-minimum-platform-version-for-spm-packages/53607