deps: update V8 to 11.5 #48456

Major V8 updates are usually API/ABI incompatible with previous versions. This commit adapts NODE_MODULE_VERSION for V8 11.5. Refs: https://github.com/nodejs/CTC/blob/master/meetings/2016-09-28.md

dllexport introduces issues when compiling with MSVC. PR-URL: nodejs#47251 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Richard Lau <[email protected]>

PR-URL: nodejs#45579 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: James M Snell <[email protected]> PR-URL: nodejs#47251 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Richard Lau <[email protected]>

It introduces process hangs on some platforms because Node.js doesn't tear down V8 correctly. Disable it while we work on a solution. Refs: nodejs#47297 Refs: https://bugs.chromium.org/p/v8/issues/detail?id=13902 PR-URL: nodejs#47450 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]>

Original commit message: [win][msvc] fix cross-compilation for arm64 Cross-compiling x64 to ARM64 on Windows fails with MSVC. The reason is the ProbeMemory function which uses asm() code prohibited in this case. This change adds conditionalizing on V8_TRAP_HANDLER_SUPPORTED thus removing the problematic parts of the code in MSVC cross-compilation. This extends https://chromium-review.googlesource.com/c/v8/v8/+/3964232 in a way, as it wraps ProbeMemory usage inside of the "#ifdef V8_TRAP_HANDLER_VIA_SIMULATOR" blocks. This follows https://chromium-review.googlesource.com/c/v8/v8/+/4403215 and https://chromium-review.googlesource.com/c/v8/v8/+/4489305 as a part of an effort to completely fix cross-compilation with MSVC. Change-Id: I59d9a995fbc8ee1cee2807429fd44d8043c178fb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4574697 Reviewed-by: Andreas Haas <[email protected]> Reviewed-by: Mark Seaborn <[email protected]> Commit-Queue: Mark Seaborn <[email protected]> Cr-Commit-Position: refs/heads/main@{#88147} Refs: v8/v8@15e31d6

Accept a new `step` break message.

`--no-harmony-sharedarraybuffer` was removed from V8 but it's still possible to disable the feature with `--enable-sharedarraybuffer-per-context`.

Provide feedback