We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
main branch
Windows
build
Compiling Node.js with ClangCL eg. running vcbuild.bat clang-cl.
vcbuild.bat clang-cl
Always.
I expect small, subtle differences between MSVC and ClangCL compilation time.
ClangCL compilation is ~2.5 slower (less with x64, more with ARM64).
The main difference is that ClangCL doesn't use precompiled headers, which MSVC does. There might be others too.
Refs: #52809
The text was updated successfully, but these errors were encountered:
Forgot to self-assign yesterday. I'm working on it and should have a PR for it this week.
Sorry, something went wrong.
build,win: enable pch for clang-cl
15bbc99
Fixes: nodejs#55208
27f8d9e
Fixes: #55208 PR-URL: #55249 Reviewed-By: Yagiz Nizipli <[email protected]>
bc5e41e
Fixes: nodejs#55208 PR-URL: nodejs#55249 Reviewed-By: Yagiz Nizipli <[email protected]>
683f348
a21be02
StefanStojanovic
Successfully merging a pull request may close this issue.
Version
main branch
Platform
Subsystem
build
What steps will reproduce the bug?
Compiling Node.js with ClangCL eg. running
vcbuild.bat clang-cl
.How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior? Why is that the expected behavior?
I expect small, subtle differences between MSVC and ClangCL compilation time.
What do you see instead?
ClangCL compilation is ~2.5 slower (less with x64, more with ARM64).
Additional information
The main difference is that ClangCL doesn't use precompiled headers, which MSVC does. There might be others too.
Refs: #52809
The text was updated successfully, but these errors were encountered: