Node: meta: V8 6.0 / TF & I tracking issue

[refack]

A reference point for things that need reevaluation after the next big V8 bump.
[edit]
Or now that TF & I is on.

[mscdex]

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?

[refack]

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.

[refack]

Quoting the [email protected] release 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.

[winksaville]

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?

[gibfahn]

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).

[refack]

@winksaville Full discussion is in https://github.com/nodejs/CTC/issues/99
The tl;dr we ported the V8 6.0 ABI into the node8 branch so we could land V8 5.9 as a minor (as will be in node8.2) and later V8 6.0.
V8 versions are landed in node soon after they land in chrome stable https://omahaproxy.appspot.com/

[winksaville]

@refack @gibfahn thanks to both of you for the info, looks promising. Is there another "issue" that I should follow to track V8 6.0?

[vsemozhetbyt]

@winksaville By the way, you can already test even V8 6.1 with Node.js canary:
https://nodejs.org/download/v8-canary/

[Trott]

[EDITING NOTE: I am going through and editing everything in this issue that refers to v8 to refer to V8 which is how the Google team stylizes it and also will (hopefully) go a small way towards avoiding confusion with Node.js 8.]

[winksaville]

@vsemozhetbyt, GREAT I'll give it a try!

[MylesBorins]

I'm closing this as a dupe as we have a handful of issues already tracking this

Comms plan: https://github.com/nodejs/CTC/issues/155
Upgrade PR: https://github.com/nodejs/node/pull/14004
V8 6.1 -> 6.0 ABI: https://github.com/nodejs/node/issues/14220

If you think this meta issue is still useful please feel free to reopen

[refack]

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).