-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
deps: V8: cherry-pick 94c87fe #27792
Conversation
Original commit message: [ic] Fix handling of +0/-0 when constant field tracking is enabled ... and ensure that runtime behaviour is in sync with the IC code. Bug: chromium:950747, v8:9113 Change-Id: Ied66c9514cbe3a4d75fc71d4fc3b19ea1538f9b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1561319 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#60768} Refs: v8/v8@94c87fe
I would like to fast track this PR to get it into a patch release tomorrow. Please +1 if you agree. |
@addaleax @devsnek @targos @bnoordhuis @nodejs/v8-update are you fine to fast track this for the patch release today? This seems like a pretty bad bug to me that should be fixed soon. |
Landed in f2fe1e5 🎉 |
Original commit message: [ic] Fix handling of +0/-0 when constant field tracking is enabled ... and ensure that runtime behaviour is in sync with the IC code. Bug: chromium:950747, v8:9113 Change-Id: Ied66c9514cbe3a4d75fc71d4fc3b19ea1538f9b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1561319 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#60768} PR-URL: nodejs#27792 Fixes: nodejs#27784 Refs: v8/v8@94c87fe Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Gus Caplan <me@gus.host>
I don't know if it's related but the linux-perf test failed: https://ci.nodejs.org/job/node-test-commit-v8-linux/2293/nodes=benchmark-ubuntu1604-intel-64,v8test=v8test/console |
Original commit message: [ic] Fix handling of +0/-0 when constant field tracking is enabled ... and ensure that runtime behaviour is in sync with the IC code. Bug: chromium:950747, v8:9113 Change-Id: Ied66c9514cbe3a4d75fc71d4fc3b19ea1538f9b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1561319 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#60768} PR-URL: #27792 Fixes: #27784 Refs: v8/v8@94c87fe Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Gus Caplan <me@gus.host>
@targos those already failed before. There is some issue around the benchmark test currently. |
Notable changes * deps: * Fix handling of +0/-0 when constant field tracking is enabled (Michaël Zasso) nodejs#27792 * Fix `os.freemem()` and `os.totalmem` correctness (cjihrig) nodejs#27718 * src: * Fix v12.3.0 regression that prevents native addons from compiling nodejs#27804 PR-URL: nodejs#27814
Original commit message:
Refs: v8/v8@94c87fe
Fixes: #27784