e77ae92738
Before this, --print-bytecode flag was available in all Release builds but did not actually print the bytecodes because OBJECT_PRINT is not set. The output was pretty confusing: [generating bytecode for function: ] 000002115442ABE9 <BytecodeArray[27]>[generating bytecode for function: main] 000002115442B069 <BytecodeArray[114]>[generating bytecode for function: Primes] 000002115442B729 <BytecodeArray[63]>[generating bytecode for function: Int32Array] 000002115442BB51 <BytecodeArray[175]>[generating bytecode for function: Primes.getPrimeCount] 000002115442BE81 <BytecodeArray[7]>[generating bytecode for function: Primes.isPrimeDivisible] 000002115442BFC9 <BytecodeArray[71]>[generating bytecode for function: Primes.addPrime] 000002115442C1C1 <BytecodeArray[31]>[generating bytecode for function: Primes.getPrime] 000002115442D7B1 <BytecodeArray[14]> With this CL, --print-bytecode flag will always output bytecode, but detailed info about constant pool and handler table are still guarded. Bug:NO Change-Id: Ie03be74520f45659303d1658da5b2acc02cf1b36 Reviewed-on: https://chromium-review.googlesource.com/497808 Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Loo Rong Jie <loorongjie@gmail.com> Cr-Commit-Position: refs/heads/master@{#45187} |
||
---|---|---|
benchmarks | ||
build_overrides | ||
docs | ||
gni | ||
gypfiles | ||
include | ||
infra | ||
samples | ||
src | ||
test | ||
testing | ||
third_party | ||
tools | ||
.clang-format | ||
.gitignore | ||
.gn | ||
.ycm_extra_conf.py | ||
AUTHORS | ||
BUILD.gn | ||
ChangeLog | ||
CODE_OF_CONDUCT.md | ||
codereview.settings | ||
DEPS | ||
LICENSE | ||
LICENSE.fdlibm | ||
LICENSE.strongtalk | ||
LICENSE.v8 | ||
LICENSE.valgrind | ||
Makefile | ||
Makefile.android | ||
OWNERS | ||
PRESUBMIT.py | ||
README.md | ||
snapshot_toolchain.gni | ||
WATCHLISTS |
V8 JavaScript Engine
V8 is Google's open source JavaScript engine.
V8 implements ECMAScript as specified in ECMA-262.
V8 is written in C++ and is used in Google Chrome, the open source browser from Google.
V8 can run standalone, or can be embedded into any C++ application.
V8 Project page: https://github.com/v8/v8/wiki
Getting the Code
Checkout depot tools, and run
fetch v8
This will checkout V8 into the directory v8
and fetch all of its dependencies.
To stay up to date, run
git pull origin
gclient sync
For fetching all branches, add the following into your remote
configuration in .git/config
:
fetch = +refs/branch-heads/*:refs/remotes/branch-heads/*
fetch = +refs/tags/*:refs/tags/*
Contributing
Please follow the instructions mentioned on the V8 wiki.