Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: V8 6.0 / TF & I tracking issue #13729

Closed
refack opened this issue Jun 16, 2017 · 12 comments
Closed

meta: V8 6.0 / TF & I tracking issue #13729

refack opened this issue Jun 16, 2017 · 12 comments
Labels
meta Issues and PRs related to the general management of the project. performance Issues and PRs related to the performance of Node.js. v8 engine Issues and PRs related to the V8 dependency.

Comments

@refack
Copy link
Contributor

refack commented Jun 16, 2017

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

@refack refack added meta Issues and PRs related to the general management of the project. performance Issues and PRs related to the performance of Node.js. v8 engine Issues and PRs related to the V8 dependency. labels Jun 16, 2017
@mscdex
Copy link
Contributor

mscdex commented Jun 16, 2017

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
Copy link
Contributor Author

refack commented Jun 16, 2017

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
Copy link
Contributor Author

refack commented Jun 16, 2017

Quoting the V8@6.0 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
Copy link

winksaville commented Jun 19, 2017

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
Copy link
Member

gibfahn commented Jun 19, 2017

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
Copy link
Contributor Author

refack commented Jun 19, 2017

@winksaville Full discussion is in nodejs/CTC#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/

@refack refack mentioned this issue Jun 19, 2017
2 tasks
@winksaville
Copy link

winksaville commented Jun 19, 2017

@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
Copy link
Contributor

vsemozhetbyt commented Jun 19, 2017

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

@Trott Trott changed the title meta: v8 6.0 / TF & I tracking issue meta: V8 6.0 / TF & I tracking issue Jun 19, 2017
@Trott
Copy link
Member

Trott commented Jun 19, 2017

[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
Copy link

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

@MylesBorins
Copy link
Contributor

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: #14220

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

@refack
Copy link
Contributor Author

refack commented Jul 18, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project. performance Issues and PRs related to the performance of Node.js. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

No branches or pull requests

7 participants