Skip to content

[cherry-pick swift/release/6.0][clang][modules] HeaderSearch::MarkFileModuleHeader sets textual headers' HeaderFileInfo non-external when it shouldn't #8905

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

ian-twilightcoder
Copy link

HeaderSearch::MarkFileModuleHeader is no longer properly checking for no-changes, and so sets the HeaderFileInfo for every textual header to non-external.

rdar://129866498

@ian-twilightcoder
Copy link
Author

Explanation: This fixes a regression from #8552 where building a module will incorrectly recreate HeaderFileInfos for textual modular headers..
Radar (and possibly SR Issue): rdar://129866498
Scope: This appears to mostly affect situations where a header is textual in one module and regular in another.
Risk: None anticipated, this restores the previous behavior where HeaderFileInfo is reused when the module map doesn't change the headers modular status.
Testing: Local testing, CI, unit test.
Reviewed By: Jan Svboda (jansvboda11)

…eModuleHeader sets textual headers' HeaderFileInfo non-external when it shouldn't

HeaderSearch::MarkFileModuleHeader is no longer properly checking for no-changes, and so sets the HeaderFileInfo for every `textual header` to non-external.

rdar://129866498
@ian-twilightcoder
Copy link
Author

@swift-ci test llvm

@ian-twilightcoder
Copy link
Author

@swift-ci test

@ian-twilightcoder
Copy link
Author

There's a few unrelated driver test failures, but otherwise I think everything looks good.

@JDevlieghere JDevlieghere merged commit 7ca683c into swiftlang:swift/release/6.0 Jun 18, 2024
3 of 5 checks passed
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.

3 participants