v8's common.gypi file expects them to be defined now. Closes #4534.
* Moved generated files to a clearer directory. * Improved detection logic for ctrpp.exe tool. Closes #4482
so that ./configure --tag=foo makes a version number like v0.9.5-foo instead of v0.9.5foo
When building custom `node` versions (e.g., floating features/fixes from different versions) it's often useful to specify a custom tag which easily identifies build when invoking `node -v`. Introduce a way to specify this tag in `node_version.h` file or by running `./configure --tag="<tag>"`. Insert it right after the patch version (and before `-pre`, if build is not a release). Closes #4452.
DTrace on Linux should not be enabled by default because not all systems will have the proper headers installed. Only enable when --with-dtrace is passed to the configure script.
Turns on -O3 and other optimizations that may produce buggy code with some toolchains. Use at your own risk.
Note that you need to start node with --gdbjit for it to become effective.
Fixes a V8 build error caused by missing arm_fpu and arm_neon settings.
Use shlex module instead of builtin string split to parse CC.
Conflicts: ChangeLog src/node_version.h test/simple/test-util-inspect.js
This makes cross-compiling easier. i.e. from my mac: ./configure --dest-cpu=arm --dest-os=linux
Conflicts: ChangeLog src/node_version.h test/message/stdin_messages.out tools/install.py
Unconditionally compile V8 with -fno-strict-aliasing on all platforms. gcc 4.5.2 on sunos generates bad code when -fstrict-aliasing is enabled, which undoubtedly means that there are more buggy versions of gcc out there. -fstrict-aliasing does not give a significant performance boost so let's just disable it. Fixes #3736.
V8 on ARM requires that armv7 is set. We don't have a good way to detect the CPU model right now so we pick a default and hope that it works okay for the majority of people. Non-scientific sampling - the ARM hardware I have lying around the house - suggests that ARMv5 and ARMv6 are still most common so armv7=0 it is. This obviously needs to be revisited sometime in the future.
Compile at -O2 and disable optimizations that trigger gcc bugs. Some people still reported mksnapshot crashes after commit b40f813 ("build: fix spurious mksnapshot crashes for good" - so much for that). Average performance of the -O2 binary is on par with the -O3 binary. Variance on the http_simple bytes/8 benchmark appears to be slightly greater but small enough that the possibly of it being noise cannot be excluded. The new binary very slightly but consistently outperforms the -O3 binary (by about 0.5%) on the mostly CPU-bound bytes/102400 benchmark. That could be an artifact of the system I benchmarked it on, a Core 2 Duo with a puny 32 kB of L1 instruction cache. The smaller binary seems to play nicer with the cache.
A variety of gcc bugs made mksnapshot crash with either a segmentation fault or a 'pure virtual method callled' run-time error. After much wailing and gnashing of teeth I managed to deduce that the bugs show up when: 1. gcc 4.5.2 for i386-pc-solaris2.11 is used and -fstrict-aliasing is enabled, or 2. gcc version 4.4.6 for x86_64-redhat-linux is used and -ffunction-sections -finline-functions at -O2 or higher is enabled Therefore, disable -ffunction-sections and -fdata-sections unconditionally and disable -fstrict-aliasing only on Solaris. The -ffunction-sections and -fdata-sections switches were nonsense anyway because we don't link with -Wl,--gc-sections.