diff options
| author | Alexandre Ganea <alex_toresh@yahoo.fr> | 2025-04-15 17:37:01 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-15 17:37:01 -0400 |
| commit | 7cb7b2d39d3b4aa984bfaeaf5e69fbfb074edd41 (patch) | |
| tree | ed21e57487d0f24c4d811b6cd1f6001ee30bb038 /clang/lib/Frontend/CompilerInstance.cpp | |
| parent | 9c73eba8aa17cb7ca4248ab1c7f67ea7ec9b50b1 (diff) | |
| download | llvm-7cb7b2d39d3b4aa984bfaeaf5e69fbfb074edd41.zip llvm-7cb7b2d39d3b4aa984bfaeaf5e69fbfb074edd41.tar.gz llvm-7cb7b2d39d3b4aa984bfaeaf5e69fbfb074edd41.tar.bz2 | |
[llvm] Build Windows release package with clang-cl if possible (#135446)
If `clang-cl.exe` and `lld-link.exe` are installed in `%PATH%`, the
Windows release build script will now use these by default, in place of
MSVC. The reason for doing this is that MSVC still has, for the past
year(s), a O(N^2) behavior when building certain LLVM source files,
which leads to long build times (minutes per file). A report was filled
here:
https://developercommunity.visualstudio.com/t/ON2-in-SparseBitVectorBase-when-com/10657991
Also added a `--force-msvc` option to the script, to use MSVC even if
clang-cl is installed.
Diffstat (limited to 'clang/lib/Frontend/CompilerInstance.cpp')
0 files changed, 0 insertions, 0 deletions