db302014b6
In gn, strict aliasing is disabled anyway. Enabling it for gyp can cause the compilation to fail on bots that still use gyp, or (even worse) can lead to miscompilation because the compiler exploits strict aliasing assumptions. R=machenbach@chromium.org Bug: chromium:628560 Change-Id: Ib756b8126a10d52f8c807ceda42dfc6dbda80ea6 Reviewed-on: https://chromium-review.googlesource.com/571806 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#46678} |
||
---|---|---|
.. | ||
mac | ||
win | ||
all.gyp | ||
coverage_wrapper.py | ||
detect_v8_host_arch.py | ||
features.gypi | ||
get_landmines.py | ||
gyp_environment.py | ||
gyp_v8 | ||
gyp_v8.py | ||
isolate.gypi | ||
landmine_utils.py | ||
landmines.py | ||
OWNERS | ||
README.txt | ||
set_clang_warning_flags.gypi | ||
shim_headers.gypi | ||
standalone.gypi | ||
sysroot_ld_flags.sh | ||
toolchain.gypi | ||
vs_toolchain.py |
For build instructions, please refer to: https://code.google.com/p/v8/wiki/BuildingWithGYP TL;DR version on *nix: $ make dependencies # Only needed once. $ make ia32.release -j8 $ make ia32.release.check # Optionally: run tests.