-
Couldn't load subscription status.
- Fork 75
[COMGR] Fix API usage per upstream changes #356
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
Since llvm#158381 the `CompilerInstance` is aware of the VFS and co-owns it. To reduce scope of that PR, the VFS was being inherited from the `FileManager` during `setFileManager()` if it wasn't configured before. However, the implementation of that setter was buggy. This PR fixes the bug, and moves us closer to the long-term goal of `CompilerInstance` requiring the VFS to be configured explicitly and owned by the instance.
|
This is my first time raising a PR to public staging. Curious to see if the PSDB displays comgr test runs. Also, not sure what the strategy is for handling reverted PRs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I will land it tomorrow after current merge lands
thx
Never mind, I now see this PR has both commits |
|
i typically clean up the revert_patches.txt later. generally let the npsdb run past lits, then kill it, and land it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok to land
No description provided.