[v16.x] deps: V8: cherry-pick d8dc66f

[luyahan]

Fix riscv64 segment fault
origin commit :

[riscv64][sparkplug] Fix sparkplug verify framesize failed

Change-Id: I7481749ba3d5c41d7405b0d88a51defbc8bec9d6
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3093009
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Reviewed-by: Ji Qiu <qiuji@iscas.ac.cn>
Commit-Queue: Yahan Lu <yahan@iscas.ac.cn>
Cr-Commit-Position: refs/heads/master@{#76277}

Refs: v8/v8@d8dc66f

[riscv64] Use s1 to save code_obj

The caller saved a4 may be clobbered by the callee function. So we substitute it with the callee saved s1 to save code_obj.

Change-Id: Iebe707cbaa62d47fdee0aa117e32e88f67dac743
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3096886
Reviewed-by: Ji Qiu <qiuji@iscas.ac.cn>
Commit-Queue: Ji Qiu <qiuji@iscas.ac.cn>
Commit-Queue: Yahan Lu <yahan@iscas.ac.cn>
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Cr-Commit-Position: refs/heads/master@{#76294}

Refs: v8/v8@3cab84c

[riscv64] Link should greater and equal zero

Change-Id: Ieeb5888efc068707766aef6ba6fc842c5deaaf9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3146673
Commit-Queue: Yahan Lu <yahan@iscas.ac.cn>
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Reviewed-by: Ji Qiu <qiuji@iscas.ac.cn>
Cr-Commit-Position: refs/heads/main@{#76784}

Refs: v8/v8@471f862

[riscv64] Add block before LoadAddress

fix node.js DCHECK failed
issue: https://github.com/riscv-collab/v8/issues/514

Change-Id: I07f40e6aca05be3eb7304a43235185fd40ebc1f2
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3260979
Reviewed-by: ji qiu <qiuji@iscas.ac.cn>
Commit-Queue: ji qiu <qiuji@iscas.ac.cn>
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Cr-Commit-Position: refs/heads/main@{#77750}

Refs: v8/v8@77599ff

[nodejs-github-bot]

Review requested:

• @nodejs/actions
• @nodejs/tsc

[luyahan]

Reland #41564 @gengjiawen @targos

[targos]

@luyahan do you target v16.x-staging because the fixes are already in v17.x ?

[luyahan]

@luyahan do you target v16.x-staging because the fixes are already in v17.x ?

Yes.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/41940/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/4472/ (✔️)

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/41957/

[luyahan]

How to fix this https://ci.nodejs.org/job/node-test-commit/51132/console?
I can't understand this output.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/41982/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/41983/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/41985/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/41988/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/41993/ (✔️)

[XieJiSS]

How to fix this https://ci.nodejs.org/job/node-test-commit/51132/console? I can't understand this output.

@luyahan Seems like a test case is failing: https://ci.nodejs.org/job/node-test-binary-windows-js-suites/RUN_SUBSET=1,nodes=win10-COMPILED_BY-vs2019/13158/console

That's strange, because this PR does not mess up with those Windows stuff.

[richardlau]

How to fix this https://ci.nodejs.org/job/node-test-commit/51132/console? I can't understand this output.

@luyahan Seems like a test case is failing: https://ci.nodejs.org/job/node-test-binary-windows-js-suites/RUN_SUBSET=1,nodes=win10-COMPILED_BY-vs2019/13158/console

You can ignore that one as it's a known flake #40728. The last CI (https://ci.nodejs.org/job/node-test-pull-request/41993/) passed.

[danielleadams]

@luyahan @targos @richardlau what is the status of this? Does this need to be backported to include the base branch/PR metadata, or can we pull this into the next 16.x as is?

[targos]

@danielleadams the changes only apply to v16.x, so we should directly pull this into the next release.

[danielleadams]

Landed in 9e68c00...036650e