Repository navigation
Conversation
On Windows, LLVM_CACHE_BUILD_SESSION_ID and -fdepscan=daemon without a socket path abort every compilation with "IO sandbox violation". The -cc1depscan client runs under the -cc1 IO sandbox, and two of its setup steps hit it on Windows: system_temp_directory() makes the socket path absolute, and ExecuteNoWait() checks the program before starting it. Neither is compiler IO, so disable the sandbox around both, as the daemon side already does.
|
Hello @tagolog 👋 Thank you for submitting a Pull Request (PR) to the LLVM Project. Since this is your first PR, here are a few useful links covering our main contribution policies and review practices.
Please reply to this message to confirm that you have read these policies, especially the LLVM AI Tool Use Policy, and that any AI tool usage has been noted in the PR description. Frequently asked questionsHow do I add reviewers? This PR will be automatically labeled, and the relevant teams will be notified. For some parts of the project, reviewers may also be added automatically. You can also add reviewers manually using the Reviewers section on this page. If you cannot use that section, it is probably because you do not have write permissions for the repository. In that case, you can request a review by tagging reviewers in a comment using What if there are no comments? If you have not received any comments on your PR after a week, you can request a review by pinging the PR with a comment such as “Ping”. The common courtesy ping rate is once a week. Please remember that you are asking for volunteer time from other developers. Are any special GitHub settings required to contribute to LLVM? We only require contributors to have a public email address associated with their GitHub commits, see this section of LLVM Developer Policy for details. If you have questions, feel free to leave a comment on this PR, or ask on LLVM Discord or LLVM Discourse. Thank you, |
tagolog
changed the title
-cc1depscan sandbox violations on Windows
|
Implemented as PR 14664 to swiftlang llvm-project |
Every -cc1 tool runs under the IO sandbox, and on Windows
system_temp_directory(),ExecuteNoWait()andExecuteAndWait()trip it.The depscan client calls the first two to find and spawn its daemon,
and -cc1depscand -execute calls the third to run its command. None of
this is compiler IO, so disable the sandbox around these calls.
This makes clang-cache sessions work on Windows and fixes these tests
in clang/test/CAS:
Add clang-cache-session-daemon.c to test the session daemon.