Repository navigation
deps: update v8 to 15.7 - #66799
deps: update v8 to 15.7#66799legendecas wants to merge 11 commits into
Conversation
|
Review requested:
|
|
Continuing in #67070 for V8 v15.8. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #66799 +/- ##
==========================================
- Coverage 92.99% 90.71% -2.29%
==========================================
Files 428 797 +369
Lines 195633 278898 +83265
Branches 30281 53634 +23353
==========================================
+ Hits 181937 252993 +71056
- Misses 13369 16258 +2889
- Partials 327 9647 +9320 🚀 New features to boost your workflow:
|
|
Updated this PR to the stable branch of V8 15.7. |
|
|
Build failed on power9le and s390x /cc @nodejs/platform-s390 @nodejs/platform-ppc |
|
@legendecas I think we need to mirror the change from a3fe991 / https://chromium-review.googlesource.com/c/v8/v8/+/8524366 in Line 73 in 8d514c7 i.e. change v8_use_metagen_instance_types=false to v8_use_metagen=false.
|
|
Hmm maybe a3fe991 is not enough. I'll take a look tomorrow. |
That only updates the gyp based build used by Node.js. The V8 CI runs V8's gn based build. FWIW in https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7472/consoleFull we can see |
Major V8 updates are usually API/ABI incompatible with previous versions. This commit adapts NODE_MODULE_VERSION for V8 15.7. Refs: https://github.com/nodejs/CTC/blob/master/meetings/2016-09-28.md
Refs: https://chromium-review.googlesource.com/c/chromium/src/+/8533406 Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com> PR-URL: nodejs#66601 Reviewed-By: Richard Lau <richard.lau@ibm.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Original commit message:
[platform] support madvise(3C) across ALL illumos revisions
In illumos, madvise(3C) now takes `void *` for its first argument
post-illumos#14418, but uses `caddr_t` pre-illumos#14418. This fix will
detect if the illumos mman.h file in use is pre-or-post-illumos#14418 so
builds can work either way.
Co-Authored-By: Dan McDonald <danmcd@mnx.io>
Refs: nodejs#65161
Change-Id: I87faa4e7042cf9b02449bd3debfdd7fed30e5d3c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8532506
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#111024}
Refs: v8/v8@5dea94c
Original commit message:
[sandbox] fix dispatch table access on illumos
illumos pointers are VA48, can allocate from the top of the 64-bit range
as well.
Co-Authored-By: Dan McDonald <danmcd@mnx.io>
Refs: nodejs#65161
Change-Id: I7d803ca0da2ab6c7cc206cb964d63683523a13da
Refs: v8/v8@011b2de
Original commit message:
Add V8_DISABLE_PRESERVE_MOST for embedders to opt out of preserve_most
preserve_most changes the calling convention, which clang
encodes in the mangled name (e.g. "U" instead of "A" for cdecl in the
Microsoft C++ ABI). A consumer whose toolchain does not support
the attribute would reference a differently mangled symbol.
This patch adds a V8_DISABLE_PRESERVE_MOST to disable it, so that
it's possible to link to V8 using different toolchains, as long
as the value of it is set consistently.
Refs: nodejs#55784
Change-Id: I67b49e739942d4026ac060be35bb39ec22256cbd
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8532546
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/main@{#111381}
Refs: v8/v8@c389861
Original commit message:
[tracing] do not define legacy tracing classes when using Perfetto
Otherwise the Windows build of Node.js fails with `undefined symbol`
errors due to the missing destructor.
Change-Id: Id0841aed2f0a8f0cfe8889c39150552e31ee5f96
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8580049
Reviewed-by: Yang Guo <yangguo@chromium.org>
Reviewed-by: Chengzhong Wu <cwu631@bloomberg.net>
Commit-Queue: Chengzhong Wu <cwu631@bloomberg.net>
Cr-Commit-Position: refs/heads/main@{#110947}
Refs: v8/v8@785a2ea
Refs: https://chromium-review.googlesource.com/c/v8/v8/+/8459484 Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
Refs: https://chromium-review.googlesource.com/c/v8/v8/+/8524366 Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com> Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net> Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
| @@ -1,5 +1,6 @@ | |||
| { | |||
| "NODE_MODULE_VERSION": [ | |||
| { "modules": 155, "runtime": "node", "variant": "v8_15.7", "versions": "28.0.0-pre" }, | |||
There was a problem hiding this comment.
I think this should follow the conclusion from nodejs/Release#1194 if this needs to be 27.0.0-pre or 28.0.0-pre.
|
Updated to V8 v15.7 stable release and this should be ready. One (blocking) issue might be the nodejs/Release#1194 that if we should carry |
joyeecheung
left a comment
There was a problem hiding this comment.
LGTM % inconclusive nodejs/Release#1194
Expected V8 v15.7 Stable Release: Nov 3, 2026.
Non-blocking upstream CLs: