-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Frontend] Improve -print-target-info #32758
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
[Frontend] Improve -print-target-info #32758
Conversation
…put. Clients that use -print-target-info can avoid an extra frontend invocation by using this information.
Describe the backward-deployment libraries via a preprocessor-driven table. Macro-metaprogramming the two places in the code base---the driver and IRGen---to use this tabble to determine which backward-compatibility libraries to link against.
The driver and any other client that attempts to properly link Swift code need to know which compatibility libraries should be linked on a per-target basis. Vend that information as part of -print-target-info.
@swift-ci please test |
@swift-ci please test source compatibility |
Build failed |
@swift-ci please test |
@swift-ci please test source compatibility |
Build failed |
Build failed |
@swift-ci test |
Build failed |
@swift-ci please smoke test |
1 similar comment
@swift-ci please smoke test |
@swift-ci please test source compatibility Release |
Enhance
-print-target-info
in a few ways to benefit the driver (and eliminate code duplication):-version
The latter involved some refactoring into a table of compatibility libraries, since we already had 2 copies of the logic in the source code, and I would have had to add a third for
-print-target-info
.