Skip to content

Fix bug with -fcas-emit-casid-file during replay. #8340

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

rastogishubham
Copy link

When using MCCAS replay with the option -fcas-emit-casid-file, we would see the error:

fatal error: caching backend error: cached output file has unknown path /file.casid

This patch fixes that issue by just having a raw_fd_ostream in the CompilerInstance that points to the .casid file rather than having it be one of the outputs of the CompilerInstance.

This patch also makes sure that the .casid file is written even if there is a ResultCallback in the MachOCASWriter.

(cherry picked from commit 2cd3dc3)

When using MCCAS replay with the option -fcas-emit-casid-file, we would
see the error:

fatal error: caching backend error: cached output file has unknown path
<path-to-file>/file.casid

This patch fixes that issue by just having a raw_fd_ostream in the
CompilerInstance that points to the .casid file rather than having it
be one of the outputs of the CompilerInstance.

This patch also makes sure that the .casid file is written even if there
is a ResultCallback in the MachOCASWriter.

(cherry picked from commit 2cd3dc3)
@rastogishubham
Copy link
Author

@swift-ci please test

@rastogishubham rastogishubham merged commit a7c0ddd into swiftlang:stable/20230725 Mar 6, 2024
@rastogishubham rastogishubham deleted the ReplayFixCASIDStable branch March 6, 2024 22:32
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