-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Move on clang LLVM #902
Comments
@ljharb What do you think about the checklist? |
I think certainly doing it for FreeBSD is good - I'm very nervous about changing how everything is compiled - but the speedup is very tempting. We'll also need to test on |
Okay I removed the checklist, but we need to solve the compilation on FreeBSD first, in fact the latest nodejs on FreeBSD doesn't need any patches, what about support compile from merged nodejs aka version greater than 1.0 from now? |
That'd be a fine start, and there's existing helpers that should allow you to do that :-) |
Okay let's give it a try. |
Manual compile test: clang llvm:
gcc:
9 min 23 sec diff in user space, about 30% time spent |
Start to work on this again. Now test nodejs v7.1.0 on Debian 8.6 amd64, with 25 threads.
Base on this result, we may try to use clang by detecting if clang exists, it'll save our time on the compilation. |
[New] `nvm install -s`: Use clang as C/C++ compiler if detected Fixes #902
[New] `nvm install -s`: Use clang as C/C++ compiler if detected Fixes nvm-sh#902
Tested on FreeBSD 10.1 64bit with nodejs v0.12.7
$ uname -a
$ c++ --version
$ g++ --version
Compilation time spent by clang LLVM:
Compilation time spent by clang GCC:
The text was updated successfully, but these errors were encountered: