-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
lib: remove simd support from util.format() #11346
Conversation
Upstream V8 is removing SIMD support. Be proactive and follow suit. Refs: https://bugs.chromium.org/p/v8/issues/detail?id=4124
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but I noticed that the v8 commit appears to have been reverted soon after landing.
should this actually go through a deprecation cycle tho? Is this still considered experimental? |
Shouldn't the second commit message use |
Because of CI failures. Temporary respite.
It's never been non-experimental. :-)
I can update that. |
cc @fhinkel - I saw you reverted the V8 CL for breaking the integration build. |
@jasnell This probably doesn't need a deprecation cycle because it never worked without |
@bnoordhuis yes, I wanted to keep the build green. I deleted the test in V8's Node fork and relanded the CL this morning, i.e., no simd.js in V8 master anymore! I think @targos usually picks up the changes on V8's node fork when updating to a newer V8 version. But I guess removing support from master before current V8 lands doesn't hurt either. +1 on removing an experimental feature without deprecation cycle. We continuously integrate V8 master in Node. If anybody's interested: CI, V8's fork of Node. |
@nodejs/ctc — do we consider changes or removal of flagged features as a semver-major or not? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Agree on calling this a semver-major even though this was experimental.
I'm good with semver-major to be on the safe side |
Not entirely related, but what is the reason for dropping |
IANAV8TM (I Am Not A V8 Team Member) but it looks like it was partially maintenance effort, partially binary size. Someone reported that the Chrome .apk shrunk by almost 500 kB after removing SIMD.js. |
PR-URL: #11346 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Ali Ijaz Sheikh <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Upstream V8 is removing SIMD support. Be proactive and follow suit. Refs: https://bugs.chromium.org/p/v8/issues/detail?id=4124 PR-URL: #11346 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Ali Ijaz Sheikh <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Landed in c5d1851...2ba4eea |
For anyone further interested: https://bugs.chromium.org/p/v8/issues/detail?id=6020&desc=2
|
Upstream V8 is removing SIMD support. Be proactive and follow suit.
Refs: https://bugs.chromium.org/p/v8/issues/detail?id=4124
I figured that since it's going away anyway, we may save ourselves some maintenance work by removing it now rather than waiting until the V8 release that drops SIMD support. (And also because I'll probably forget if I don't act on it immediately.)
If people feel it's premature, I'm happy to postpone. The first commit does some minor cleanup and can land either way.