Repository navigation
meta: V8 6.0 / TF & I tracking issue #13729
Description
Activity
I'm not sure what you mean, TurboFan + Ignition is already the default in V8 5.9 which is in master. Unless there are specific "issues" with 6.0?
I'm not sure what you mean, TurboFan + Ignition is already the default in V8 5.9 which is in master. Unless there are specific "issues" with 6.0?
I saw some issues that concluded with "let's wait for V8 to get better", and thought It would be good to track them. Either old issues that could be reevaluated now, or recent issues that will need reevaluation after 6.0.
Quoting the
V8@6.0release post:ES6 Performance
V8 6.0 continues to improve performance of ES2015 features. This release contains optimizations to language feature implementations that overall result in a roughly 10% improvement in V8’s ARES-6 score.
I'm working with WebAssembly and V8 6.0 lands ShareArrayBuffers which I'd like to be able to use with node:
V8 6.0 introduces support for SharedArrayBuffer, a low-level mechanism to share memory between JavaScript workers and synchronize control flow across workers. SharedArrayBuffers give JavaScript access to shared memory, atomics, and futexes. SharedArrayBuffers also unlock the ability to port threaded applications to the web via asm.js or WebAssembly.
What is the current release plan for V8 6.0?
What is the current release plan for V8 6.0?
Should go into a future Node 8 release (before Node 8 goes LTS in October).
Reacted by Refael Ackermann and Moritz MahringerReacted by Moritz Mahringer and Markus PadourekReacted by Moritz Mahringer@winksaville Full discussion is in nodejs/CTC#99
The tl;dr we ported theV8 6.0ABI into thenode8branch so we could landV8 5.9as a minor (as will be innode8.2) and laterV8 6.0.
V8versions are landed in node soon after they land inchrome stablehttps://omahaproxy.appspot.com/@winksaville By the way, you can already test even V8 6.1 with Node.js canary:
https://nodejs.org/download/v8-canary/- changed the title
[-]meta: v8 6.0 / TF & I tracking issue[/-][+]meta: V8 6.0 / TF & I tracking issue[/+]on Jun 19, 2017 [EDITING NOTE: I am going through and editing everything in this issue that refers to
v8to refer toV8which is how the Google team stylizes it and also will (hopefully) go a small way towards avoiding confusion with Node.js 8.]Reacted by Gibson Fahnestock, Refael Ackermann, Vse Mozhe Buty and Moritz MahringerReacted by Gibson Fahnestock and Moritz Mahringer@vsemozhetbyt, GREAT I'll give it a try!
I'm closing this as a dupe as we have a handful of issues already tracking this
Comms plan: nodejs/CTC#155
Upgrade PR: #14004
V8 6.1 -> 6.0 ABI: #14220If you think this meta issue is still useful please feel free to reopen
If you think this meta issue is still useful please feel free to reopen
Turns out I used it way less then expected, so closed is right. (and anyway could still be used for tracking without causing confusion).
A reference point for things that need reevaluation after the next big V8 bump.
[edit]
Or now that TF & I is on.