v8: forward compatibility to current V8 master
As discussed in https://github.com/nodejs/CTC/issues/99, we are aiming for a upgrade to V8 6.0 in the Node 8.x lifecycle. Therefore, it makes sense to apply changes that are semver-major because they break the API or ABI before that upgrade actually happens.
Changes that are marked deps:
are cherry-picks, the rest is manual work and needs review.
This is a bit WIP because I’m still compiling to see if everything works out. ;)
CI: https://ci.nodejs.org/job/node-test-commit/9702/
CI: https://ci.nodejs.org/job/node-test-commit/9705/
CI: https://ci.nodejs.org/job/node-test-commit/9720/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/683/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/685/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/686/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/687/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/691/
CITGM: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/763/
CITGM on master for comparison: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/764/
@nodejs/v8 @targos @jasnell
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
commit message follows commit guidelines -
figure out whether to do anything about removed command line flags
Affected core subsystem(s)
deps/v8