-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
Improve ClangCL compilation time on Windows. #55208
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Forgot to self-assign yesterday. I'm working on it and should have a PR for it this week. |
StefanStojanovic
added a commit
to JaneaSystems/node
that referenced
this issue
Oct 3, 2024
louwers
pushed a commit
to louwers/node
that referenced
this issue
Nov 2, 2024
Fixes: nodejs#55208 PR-URL: nodejs#55249 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
tpoisseau
pushed a commit
to tpoisseau/node
that referenced
this issue
Nov 21, 2024
Fixes: nodejs#55208 PR-URL: nodejs#55249 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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: