Skip to content

Eng/pr swift frontend tweaks for caching #65925

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

cachemeifyoucan
Copy link
Contributor

This PR contains some tweaks to swift-frontend to smooth out some edges in order to land caching PRs.

@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please test windows platform

When pch are explicitly created, there is no need to cached produced pch
in memory since pch is only going to be consumed by a later process.
Don't add cxx shim when c++ interop is not used. This is to cut down the
unnecessary dependencies that are not seen by the dependency scanner.
When creating ClangImporter directly from cc1 args, there is no need for
clang path, and it might even be mistaken as an input path. Don't use
clang executable path in the arguments when creating from cc1 commands.
When using explicit module build, there is no need to check top level
module map to see if the module exists or not, since dependency scanning
already pulled in all needed modules. Furthermore, when using clang
include tree, the module maps are not available through FS for this
search. Just directly try to load modules when using explicit module
build.
@cachemeifyoucan cachemeifyoucan force-pushed the eng/PR-swift-frontend-tweaks-for-caching branch from d8efab5 to f4569a6 Compare May 16, 2023 23:40
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

@cachemeifyoucan cachemeifyoucan merged commit c2c2414 into swiftlang:main May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants