Skip to content

[5.0][ClangImporter] Fix issue with source order comparisons of clang source locations when using a bridging PCH #21956

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 1 commit into from
Jan 17, 2019

Conversation

akyrtzi
Copy link
Contributor

@akyrtzi akyrtzi commented Jan 17, 2019

Clang importer was picking the beginning of the main FileID as include location of its modules, which is the same location that the clang PCH mechanism is using as import location.
Make sure to use a different location otherwise we'll have problems with source order comparisons of clang source locations not being deterministic.

rdar://29137319

master: #21952

…ce locations when using a bridging PCH

Clang importer was picking the beginning of the main FileID as include location of its modules, which is the same location that the clang PCH mechanism is using as import location.
Make sure to use a different location otherwise we'll have problems with source order comparisons of clang source locations not being deterministic.

rdar://29137319
@akyrtzi akyrtzi requested a review from a team as a code owner January 17, 2019 21:17
@akyrtzi
Copy link
Contributor Author

akyrtzi commented Jan 17, 2019

@swift-ci Please test

@akyrtzi akyrtzi merged commit a303a07 into swiftlang:swift-5.0-branch Jan 17, 2019
@akyrtzi akyrtzi deleted the 5.0-import-loc-pch branch January 17, 2019 23:49
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.

1 participant