v8/node/vee-eight-lkgr has just updated v8 to 5.9 with Ignition+TurboFan turned on by default.
Node.js 8.0 has a chance to be released with at most v8 5.8.
Would v8 5.9 be considered as semver-major due to the new interpreter/compiler pipeline? Has it a chance to be added into Node.js 8.0 later?
vsemozhetbyt
All 4 comments
Would v8 5.9 be considered as semver-major due to the new interpreter/compiler pipeline?
IMO the new pipeline itself does not make the update semver-major. No code should be broken by the switch (if it happens, it's a V8 bug).
Has it a chance to be added into Node.js 8.0 later?
It depends on multiple things. Somebody would have write a patch to make the update ABI/API compatible with 5.7 or 5.8 (depending on the version that will ship with Node 8).
I think performance will also be an important thing to check.
targos
on 13 Mar 2017
Benchmarks (to be continued): https://github.com/nodejs/node/issues/11851
vsemozhetbyt
on 14 Mar 2017
@Fishrock123 you ask yesterday on IRC about this.
italoacasas
on 15 Mar 2017
Beyond the normal ABI compatibility concerns, one of the key considerations for landing any v8 greater than 5.8 in 8.x will be whether or not the new pipeline is something we want to support in the LTS line post October. Up to this point, several of the @nodejs/v8 folks have been urging restraint moving up while they make sure everything is good.
jasnell
on 15 Mar 2017
Related issues
sandeepks1
路
3Comments
cong88
路
3Comments
addaleax
路
3Comments
danialkhansari
路
3Comments
dfahlander
路
3Comments
Most helpful comment
IMO the new pipeline itself does not make the update semver-major. No code should be broken by the switch (if it happens, it's a V8 bug).
It depends on multiple things. Somebody would have write a patch to make the update ABI/API compatible with 5.7 or 5.8 (depending on the version that will ship with Node 8).
I think performance will also be an important thing to check.