Skip to content
Commits on Jan 11, 2013
  1. @TooTallNate

    configure: define "arm_fpu" and "arm_neon" for ARM

    TooTallNate committed
    v8's common.gypi file expects them to be defined now.
    Closes #4534.
Commits on Jan 3, 2013
  1. @sblom @piscisaureus

    windows: improve Visual Studio Express build support

    sblom committed with piscisaureus
    * Moved generated files to a clearer directory.
    * Improved detection logic for ctrpp.exe tool.
    Closes #4482
Commits on Dec 27, 2012
  1. @isaacs

    build: Add hyphen to custom build tags

    isaacs committed
    so that ./configure --tag=foo makes a version number like v0.9.5-foo
    instead of v0.9.5foo
Commits on Dec 21, 2012
  1. @mmalecki @TooTallNate

    build: allow to specify custom tags

    mmalecki committed with TooTallNate
    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.
  2. @sblom @isaacs
Commits on Nov 21, 2012
  1. @sblom @piscisaureus

    windows: add tracing with performance counters

    sblom committed with piscisaureus
    Patch by Henry Rawas and Scott Blomquist.
Commits on Nov 20, 2012
  1. @bnoordhuis
Commits on Nov 16, 2012
  1. @sgallagher @bnoordhuis
Commits on Nov 5, 2012
  1. @tjfontaine @bnoordhuis
  2. @sgallagher @bnoordhuis
  3. @sgallagher @bnoordhuis
Commits on Nov 1, 2012
  1. @shigeki @bnoordhuis

    build: fix default dtrace flag on Linux

    shigeki committed with bnoordhuis
    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.
  2. @bnoordhuis
  3. @bnoordhuis

    tracing: add systemtap support

    Jan Wynholds committed with bnoordhuis
Commits on Oct 31, 2012
  1. @fredericosilva @piscisaureus
Commits on Oct 25, 2012
  1. @bnoordhuis

    Merge remote-tracking branch 'origin/v0.8'

    bnoordhuis committed
Commits on Oct 24, 2012
  1. @bnoordhuis

    build: add --unsafe-optimizations configure switch

    bnoordhuis committed
    Turns on -O3 and other optimizations that may produce buggy code with some
    toolchains. Use at your own risk.
Commits on Oct 23, 2012
  1. @bnoordhuis

    build: re-enable gdbjit, honor --gdb again

    bnoordhuis committed
    Note that you need to start node with --gdbjit for it to become effective.
Commits on Oct 15, 2012
  1. @bnoordhuis

    configure: turn on VFPv3 on ARMv7

    bnoordhuis committed
    Fixes a V8 build error caused by missing arm_fpu and arm_neon settings.
    This is a back-port of commit bbf6b4e from the master branch.
    Fixes #4142.
Commits on Sep 19, 2012
  1. @bnoordhuis

    configure: turn on VFPv3 on ARMv7

    bnoordhuis committed
    Fixes a V8 build error caused by missing arm_fpu and arm_neon settings.
Commits on Sep 17, 2012
  1. @Hello71 @bnoordhuis

    configure: always use shlex instead of split

    Hello71 committed with bnoordhuis
    Use shlex module instead of builtin string split to parse CC.
Commits on Sep 12, 2012
  1. @isaacs

    Merge remote-tracking branch 'ry/v0.8' into master

    isaacs committed
Commits on Sep 9, 2012
  1. @TooTallNate

    configure: add a "--dest-os" option to force a gyp "flavor"

    TooTallNate committed
    This makes cross-compiling easier. i.e. from my mac:
        ./configure --dest-cpu=arm --dest-os=linux
Commits on Sep 4, 2012
  1. @bnoordhuis
  2. @tjfontaine @bnoordhuis
Commits on Aug 17, 2012
  1. @bnoordhuis

    Merge remote-tracking branch 'origin/v0.8'

    bnoordhuis committed
Commits on Aug 15, 2012
  1. @isaacs
Commits on Aug 14, 2012
  1. @bnoordhuis
Commits on Aug 13, 2012
  1. @bnoordhuis
Commits on Jul 26, 2012
  1. @adammw @bnoordhuis
Commits on Jul 18, 2012
  1. @bnoordhuis

    build: fix mksnapshot crash on sunos

    bnoordhuis committed
    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.
Commits on Jul 12, 2012
  1. @bnoordhuis

    build: partially fix configure on ARM

    bnoordhuis committed
    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.
  2. @bnoordhuis

    build: disable unsafe optimizations

    bnoordhuis committed
    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.
Commits on Jul 11, 2012
  1. @bnoordhuis

    build: fix spurious mksnapshot crashes for good

    bnoordhuis committed
    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.
Commits on Jul 7, 2012
  1. @piscisaureus

    Fix the Windows build

    piscisaureus committed
Something went wrong with that request. Please try again.