Skip to content

[Caching] Embed bridging header in binary module correctly when caching #72804

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

Merged
merged 2 commits into from
Apr 16, 2024

Conversation

cachemeifyoucan
Copy link
Contributor

When caching is enabled with include-tree, the bridging header PCH is created from the include tree directly. Setup the rewriter correctly when embedding the bridging header into swift binary module.

rdar://125719747

@cachemeifyoucan
Copy link
Contributor Author

Need clang change here: swiftlang/llvm-project#8531

@xedin xedin removed their request for review April 9, 2024 17:30
@cachemeifyoucan
Copy link
Contributor Author

Please test with following pull request:
swiftlang/llvm-project#8531

@swift-ci please smoke test

@cachemeifyoucan
Copy link
Contributor Author

Please test with following pull request:
swiftlang/llvm-project#8531

@swift-ci please smoke test linux platform

When caching is enabled with include-tree, the bridging header PCH is
created from the include tree directly. Setup the rewriter correctly
when embedding the bridging header into swift binary module.

rdar://125719747
The binary module built from a CAS build will have the embeded bridging
header info with 0 modTime. Allow a regular build to import such a
module with the same behavior as if the module is built from a regular
build.

rdar://126221616
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

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