Michaël Zasso
ec02b811a8
deps: update V8 to 5.4.500.27
...
Pick up latest commit from the 5.4-lkgr branch.
deps: edit V8 gitignore to allow trace event copy
deps: update V8 trace event to 315bf1e2d45be7d53346c31cfcc37424a32c30c8
deps: edit V8 gitignore to allow gtest_prod.h copy
deps: update V8 gtest to 6f8a66431cb592dad629028a50b3dd418a408c87
PR-URL: https://github.com/nodejs/node/pull/8317
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com>
2016-09-22 09:51:19 +02:00
Michaël Zasso
d8011d1683
deps: upgrade V8 to 4.6.85.23
...
PR-URL: https://github.com/nodejs/node/pull/3351
Reviewed-By: indutny - Fedor Indutny <fedor.indutny@gmail.com>
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
2015-10-14 11:20:34 -07:00
Ali Ijaz Sheikh
9fddd83cf9
deps: upgrade V8 to 4.5.103.24
...
Upgrade to the latest branch-head for V8 4.5. For the full commit log see
https://github.com/v8/v8-git-mirror/commits/4.5.103.24
PR-URL: https://github.com/nodejs/node/pull/2509
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
2015-09-06 21:38:01 +10:00
Ryan Dahl
0bca54444a
Upgrade V8 to 3.6.1
2011-09-07 21:23:29 -07:00
Ryan Dahl
e5564a3f29
Upgrade V8 to 3.4.10
2011-07-08 16:40:11 -07:00
Ryan Dahl
149562555c
Downgrade V8 to 3.1.8.25
...
There are serious performance regressions both in V8 and our own legacy
networking stack. Until we correct our own problems we are going back to the
old V8.
2011-07-05 14:51:29 -07:00
Ryan Dahl
6054dcc130
Upgrade V8 to 3.4.9
2011-07-05 11:41:56 -07:00
